This repository has been archived by the owner on Mar 26, 2024. It is now read-only.
Add an MSRV policy to the README #116
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elasticdog
force-pushed
the
push-xywsotqrmqks
branch
from
9946a14
to
42a1c03
Compare
This is a bit of a tricky topic, as the Rust ecosystem is waiting on better Cargo support to make usability better, and there are a lot of differing opinions and theories on how best to handle an MSRV. Not a lot of concrete data out there. The Rust compiler itself explicitly only supports the latest stable version, so any MSRV policy is essentially how long you're willing to wait for dependents of your library to upgrade before you adopt new features. Artificially holding this back might also mean missing out on security fixes, and I'm a big fan of staying current when possible. This can always be changed, but I wanted to have something in place to make sure that it's covered. See: - rust-lang/libs-team#72 - time-rs/time#535
elasticdog
force-pushed
the
push-xywsotqrmqks
branch
from
42a1c03
to
0695bf3
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a bit of a tricky topic, as the Rust ecosystem is waiting on better Cargo support to make usability better, and there are a lot of differing opinions and theories on how best to handle an MSRV. Not a lot of concrete data out there. The Rust compiler itself explicitly only supports the latest stable version, so any MSRV policy is essentially how long you're willing to wait for dependents of your library to upgrade before you adopt new features. Artificially holding this back might also mean missing out on security fixes, and I'm a big fan of staying current when possible.
This can always be changed, but I wanted to have something in place to make sure that it's covered.
See:
Checklist
cargo xtask fixupfor project formatting and styleCHANGELOG.mdper "Keep a Changelog" format