-
Notifications
You must be signed in to change notification settings - Fork 218
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
imp: in fixed-hash
allow opting out rand
when std
enabled
#804
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.
This is a breaking change unfortunately.
We'd also need to bump MSRV to 1.60 here according to https://doc.rust-lang.org/cargo/reference/features.html#dependency-features:
Note: The ? syntax is only available starting with Rust 1.60.
We don't have an automatic check for MSRV currently..
@ordian what is next if you know? think is that this thing (along with others) hampers adoption of non browser std wasm usage of these things. and before that was annoying in usage in pure parity codebase (that js compilation issue) |
Tests are failing (exactly because this is a breaking change). They need to be fixed, then it can be merged and later released as a breaking change. But I am not sure why you are blocked on this. I don't see any |
When I use this crate with std it makes wasm32 std project fail to compile. If use in wasm32 std but not setting std only on this crates it works. But breaks right away as dep of dep because this crate is used a lot, and sets honestly srt on this crate. |
Yeah, sometimes you can't control which features are selected due to transitive dependencies and cargo's feature unification. |
seems tests are failing
|
Co-authored-by: Bastian Köcher <git@kchr.de>
Closes: #805