-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
upgrade to rust 1.85 #3216
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
base: master
Are you sure you want to change the base?
upgrade to rust 1.85 #3216
Conversation
Changing the MSRV to 1.85, without a good reason, will make |
Why not use rustup to get easy access to the latest Rust version? |
For private or development use, that is indeed a good solution. However for stable Linux distributions (e.g. debian, RHEL, Ubuntu) the Rust toolchain is updated in longer cycles. In those cases, if the MSRV is set to a higher version then |
Why is not bat also updated in longer cycles in that case? Users of such distros by definition value stability over bleeding edge, don't they? The reason I am asking these questions is because there is a cost (both in time and in "fun factor") of keeping MSRV low. So I hope we can find a pragmatic approach. |
I actually do that but there are some corner cases that could break the build. Sometimes a new distribution release gets branched before a Rust update and you get stuck with an old Rust version until the next big release. This makes it not possible to update
I am 100% with you on this. You should not forcibly keep the MSRV low, just don't update it if you don't have to. Sometimes a dependency forces you to raise the MSRV because that dependency requires a new language feature. Maybe you guys are the ones that want to use new language features. These are all valid reasons. I just wanted to shed some light on why raising the MSRV without a valid reason could be bad. |
upgrade to rust 1.85