We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, I primarily use nalgebra for mathematics code and then convert into the glam format afterwards.
However, using three_d::* creates a naming collision not just with nalgebra, but with other math libraries.
three_d::*
Would you consider the re-exported math code being under a three_d::math::* import, which would make back and forth code easier to use?
three_d::math::*
The text was updated successfully, but these errors were encountered:
Yeah, that's a good idea 👍
Sorry, something went wrong.
No branches or pull requests
Hi, I primarily use nalgebra for mathematics code and then convert into the glam format afterwards.
However, using
three_d::*
creates a naming collision not just with nalgebra, but with other math libraries.Would you consider the re-exported math code being under a
three_d::math::*
import, which would make back and forth code easier to use?The text was updated successfully, but these errors were encountered: