Skip to content
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

Merged
merged 3 commits into from
Oct 20, 2023
Merged

Conversation

preston-evans98
Copy link
Member

Description

Currently, all of our cargo.tomls specify a rust-version even though we have rust-toolchain.toml file. This removes that redundancy.

@codecov
Copy link

codecov bot commented Oct 20, 2023

Codecov Report

Merging #1078 (553c6d9) into nightly (08e842f) will decrease coverage by 0.1%.
The diff coverage is n/a.

see 2 files with indirect coverage changes

@preston-evans98
Copy link
Member Author

cc @neysofu @vlopes11, do either of you see any downsides here? I think these are just redundant, but don't remember why they were added

@neysofu
Copy link
Member

neysofu commented Oct 20, 2023

rust-toolchain.toml specifies the intended Rust toolchain to develop the workspace in, whereas rust-version lets downstream users know the minimum required rustc version to be able to use the package.

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 rust-version will inevitably get out of sync, just like in our case. I'm in favor of removing it. It would be ideal to reintroduce it once we're confident we can provide correct values: #1081.

Copy link
Contributor

@vlopes11 vlopes11 left a 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

adapters/risc0/Cargo.toml Show resolved Hide resolved
@citizen-stig
Copy link
Member

rust-toolchain.toml specifies the intended Rust toolchain to develop the workspace in, whereas rust-version lets downstream users know the minimum required rustc version to be able to use the package.

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 rust-version will inevitably get out of sync, just like in our case. I'm in favor of removing it. It would be ideal to reintroduce it once we're confident we can provide correct values: #1081.

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.

@preston-evans98
Copy link
Member Author

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.

@preston-evans98 preston-evans98 added this pull request to the merge queue Oct 20, 2023
Merged via the queue into nightly with commit 9908444 Oct 20, 2023
13 checks passed
@preston-evans98 preston-evans98 deleted the preston/rust-version branch October 20, 2023 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants