-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
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
Fix full no_std compatibility #67
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few questions to understand, plus I assuming this is solely needed at this moment due to dusk-plonk in no-std is that correct?
In that case, I will postpone the release of bls as well to the next iteration, however I would fix the broken_intra_doc_links (so I would create a different PR for that, as you did for jubjub)
Cargo.toml
Outdated
dusk-bytes = "0.1" | ||
dusk-bls12_381 = {version="0.6", default-features=false} | ||
subtle = {version="^2.3", default-features = false} | ||
rand_core = {version = "0.5", default-features=false} | ||
subtle = {version="2.0", default-features = false} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Care to elaborate this downgrade…?
What are we gaining, what are we losing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nevermid. Will bring it back.
subtle = {version="^2.3", default-features = false} | ||
rand_core = {version = "0.5", default-features=false} | ||
subtle = {version="2.0", default-features = false} | ||
rand_core = {version = "0.6", default-features=false} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it needed to be updated? Why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To make it no_std compatible with the new random crates. This seems to be the direction that Rust ecosystem is taking. Moving away from rand
to rand_core
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Resolves: #66
NOTE Will merge as soon as dusk-network/bls12_381#55 is merged