Updated to nalgebra 0.31, Fixed wasm support by indirectly enabling the 'js' feature as fallbac… #380
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So this seems to be a bottleneck towards updating the nalgebra version, which is having issues for upstream crates. I noticed that the only thing preventing a direct upgrade was this error
Which after some searching, was an issue with the
randcrate relying ongetrandomand its "js" feature. After following the Indirect Dependencies steps, all of the tests incargo testpassed and the CircleCI passed.Hopefully this should be a relatively instant PR for updating nalgebra to the latest version.