MSRV 1.64 & Workspace inheritance for dependencies #4344
Merged
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.
The first two commits are just bumping the MSRV and fixing the clippy lints.
The last commit is more involved. I'm using the new workspace inheritance method for declaring dependencies. This means that we have a global list of dependencies in the root
Cargo.toml
that the other crates refer to. If we then want to, for example, bump the version a dependency, we only need to change the version in rootCargo.toml
. I think it also creates a clear overview of (almost) all dependencies in the project. There were also many dependencies for which the spec was outdated or where one crate specified it as "0.2" and another as "0.2.3".I can remove this last commit if you want, but I think it's useful. @sylvestre