Merged
Conversation
Created using spr 1.3.6-beta.1
iliana
approved these changes
Mar 3, 2025
Contributor
iliana
left a comment
iliana
left a comment
There was a problem hiding this comment.
LGTM, although the improvement in resolver v3 shouldn't affect us since we stay on the latest stable compiler fairly consistently.
Contributor
Author
Yeah absolutely -- I just realized this while filling out the steps for RFD 500. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cargo resolver version 3 introduces an MSRV-aware resolver. Unlike the change from resolver v1 to v2, there are no changes to packages or feature sets that get built.