-
Notifications
You must be signed in to change notification settings - Fork 301
Follow up 844 #858
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
base: master
Are you sure you want to change the base?
Follow up 844 #858
Conversation
d55eb2f
to
f4d8fb4
Compare
Needs #860 to get past CI. |
In 3f6c383: You can't reexport the same symbol with different types based on a feature gate. This makes the features non-additive. Why export these? |
f4d8fb4 looks good otherwise. |
Oooph, of course. |
ping @tcharding |
AFAICT the type is set exactly by the feature #[cfg_attr(feature = "std", path = "internal_std.rs")]
#[cfg_attr(not(feature = "std"), path = "internal_nostd.rs")]
mod internal;
#[cfg(not(feature = "std"))]
mod spinlock;
pub use internal::{
rerandomize_global_context, with_global_context, with_raw_global_context, SECP256K1,
}; |
Delete the old global context, make the new ones `pub`, and re-export them in the `context` modulue (implies they are also re-exported at crate root). Exactly which one is re-exported depends on whether the crate is built with `std` or not.
Now that we fully use the new global contexts that work both with and without `std` we can delete the `global-context` and `global-context-less-secure` features.
One stale construction of a context in docs, remove it.
f4d8fb4
to
c42691c
Compare
Rebased to see if lint warnings go away. No other changes. |
Found by clippy.
At first we deprecated these but since we have a global context that works with and without `std` and we deleted the `global-context` feature we might as well just clobber these 2 functions now also.
c42691c
to
72a115f
Compare
If |
oooo, I get it. You build with no-std, get one type, then someone else in your stack enables std and you get borked. |
This does everything in the issue description of #850. I'm not sure why I opened #856 also, and I'm confused by the first two check points of 856 as well.
Follow up #844.
Close #850