-
Notifications
You must be signed in to change notification settings - Fork 49
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
Minimum Supported Rust Version (MSRV) Policy? #203
Comments
See also rust-lang/libs-team#72 (comment) on how to check with |
I would vote for 12 months timeframe, no more. I made some strong statements about a fixed MSRV for bytemuck and tinyvec, and it's not impossible to stand by them. but it's inconvenient to stick with them eternally. A rolling window lets you eventually adapt to rust updates without cfg all over your crate, while a large rolling window lets you stay compatible with linux distros. Even SDL2, famed for its long term compatibility, will bump its requirements over time. |
Something I've learned is that 12 months might not be enough for some LTS-style situations.
(note: the above is purely descriptive, not prescriptive one way or another) |
For my crates, I usually try to keep the MSRV at or below Debian Stable, but I don't think that will be desired or even possible for this crate. As it's "experimental" for the time being, I think it'd be fine to have an undefined MSRV. But, eventually, it would be nice to pin it to either a timed MSRV (12 months is usually fine) or some distro's Rust version (Debian Testing uses 1.56 as of the time of writing). |
Any bump will also have to be within Firefox' MSRV, if we want |
This library should probably settle on some kind of MSRV policy, I would like some input on that?
A few options:
Notes:
mrustc
supports 1.54 (as of july 2022)objc-sys
supports "N-10" whileobjc2
supports "N-3")extern "C-unwind"
would take longer to make defaultcargo
/rustc
"):libc
discussion: MSRV policy for libc crate rust-lang/libs-team#72winit
discussion: Minimum Supported Rust Version rust-windowing/winit#1075rustc
usingrustup
or MacPorts, maybe the situation is a bit different?rustc
features, doesn't if we're using newercargo
featurescc
,libc
,malloc_buf
anduuid
) would have to have a policy that matches ours!The text was updated successfully, but these errors were encountered: