-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
[Crater run experiment] let-chain rescoping #125151
[Crater run experiment] let-chain rescoping #125151
Conversation
r? @Nadrieril rustbot has assigned @Nadrieril. Use |
The job Click to see the possible cause of the failure (guessed by this bot)
|
I'm on vacation for a week, I'll let someone else figure out the right crater incantation. r? compiler |
@bors try |
…rater-runner, r=<try> [Crater run experiment] let-chain rescoping Please do not merge this PR. This is only for crater run experimentation. I would like to nominate a crater run for rust-lang#107251 assuming that the feature gate is always on. Through this experiment, we hope to collect breakage in the wild. We would focus on both compilation errors and test errors that this edition change can lead to, if users are targeting Edition 2024 and writing code assuming the old semantics unknowingly. I realise that some tests may not work well if an edition switch happens. I am fixing them in the main PR.
☀️ Try build successful - checks-actions |
I would like to run @ |
@craterbot build-and-test |
🚨 Error: failed to parse the command 🆘 If you have any trouble with Crater please ping |
@craterbot run mode=build-and-test |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
We'd need to improve the diagnostic if we make this change, but not terrible. There impact is larger than I'd be personally comfortable, but also small enough that it might be acceptable after fixing
|
FTR the first version of smodel on crates.io, 0.1.0 was released one month ago, April 29 2024. |
@dingxiangfei2009 are we ok to close this PR now? |
@estebank Sorry, yes. Let's. |
Please do not merge this PR. This is only for crater run experimentation.
I would like to nominate a crater run for #107251 assuming that the feature gate is always on. Through this experiment, we hope to collect breakage in the wild. We would focus on both compilation errors and test errors that this edition change can lead to, if users are targeting Edition 2024 and writing code assuming the old semantics unknowingly.
I realise that some tests may not work well if an edition switch happens. I am fixing them in the main PR.
Tracking:
else
#124085