-
Notifications
You must be signed in to change notification settings - Fork 105
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
Remove rust-version from cargo files #1078
Conversation
It's a good thing to have both, but only if checked in CI with a tool like https://github.com/foresterre/cargo-msrv, otherwise |
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.
Agreed with @neysofu . We do enforce stable
, and that should suffice for us, as stable
versions will upgrade passively over time (i.e. release train).
Unless there is an explicit reason to bind ourselves to an older stable
(i.e. 1.66
), we shouldn't do that
I agree that checking MSRV is good thing, but I believe that at this moment of rapid changes of the repo it might slow as down. So I am voting to remove rust_version now and re-untroduce it later. Because with MSRV we will also have to respect MSRV of core dependencies. |
Ah, I'd forgotten this was used for MSRV checks. Yeah, we definitely need at least 1.70 already and will probably keep bumping that for a while. But agreed, let's add this back as things stabilize. |
Description
Currently, all of our
cargo.toml
s specify arust-version
even though we haverust-toolchain.toml
file. This removes that redundancy.