You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 1.0 release should guarantee that it builds with a specific Rust version (and later), so new minor versions of our crate don't break when building with the same Rust compiler.
We should also add a Travis test for that specific version in addition to "stable".
Activity
crumblingstatue commentedon May 9, 2017
I would really like to wait for at least
associated_consts
andpub_restricted
in Rust to stabilize before making the commitment.pub_restricted
will most likely be stable in Rust 1.18. I'm not sure aboutassociated_consts
.crumblingstatue commentedon Jul 12, 2017
associated_consts
will be stable in 1.20.I'm setting 1.20 as a target for stabilization.
crumblingstatue commentedon Sep 7, 2017
Hmm... Might want to wait until extern types are stable, as using empty enums for the various
Ref
types might be unsound.crumblingstatue commentedon Jan 7, 2018
#[repr(transparent)]
could also be used to wrap the bindgen generated types instead of declaring separate extern types.EDIT:
repr(transparent)
requires non-zero sized types, and bindgen generates a zero-sized type.I think until
extern_types
are stable, I'll just copy what bindgen does and put a_unused: [u8; 0]
field in these types.crumblingstatue commentedon Oct 6, 2024
Honestly, most Rust crates just update their MSRV willy-nillly, so I don't see any reason why we should do otherwise.