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

OnceLock is stabilized in 1.70.0 but current MSRV is 1.67.1 #284

Closed
rnbguy opened this issue Nov 13, 2024 · 2 comments
Closed

OnceLock is stabilized in 1.70.0 but current MSRV is 1.67.1 #284

rnbguy opened this issue Nov 13, 2024 · 2 comments

Comments

@rnbguy
Copy link
Contributor

rnbguy commented Nov 13, 2024

#237 introduces the use of OnceLock

static CELL: std::sync::OnceLock<#t> =
std::sync::OnceLock::new();

But OnceLock is stabilized in 1.70.0. Shouldn't the MSRV of rstest be 1.70.0 ?

@la10736
Copy link
Owner

la10736 commented Nov 13, 2024

You're right 😢

I trusted cargo hack check --rust-version --workspace --ignore-private but maybe it use just the provided msrv from the other packages.... I need to change it.

Thank to report it

@rnbguy
Copy link
Contributor Author

rnbguy commented Nov 13, 2024

Thanks for quick reply 🙂

I think, it is a bit nuanced to find the breakage via MSRV finder (I use cargo-msrv) - because OnceLock is not being used inside rstest - it is only imported inside the macro generated code.

I think, it would be better to include running the tests at the MSRV version 😉

- name: Run tests stable
run: RSTEST_TEST_CHANNEL=stable cargo test --all --verbose
- name: Run tests beta
run: RSTEST_TEST_CHANNEL=beta cargo test --all --verbose
- name: Run tests nightly
run: RSTEST_TEST_CHANNEL=nightly cargo test --all --verbose

PS. I found out about this via cargo +nightly clippy which is autoconfigured in my IDE.

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

No branches or pull requests

2 participants