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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does the equal force it, I thought just specifying a dep with a version was enough
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought so too! Apparently omitting it equals
^
, which is basically means:1.2.3 := >=1.2.3, <2.0.0
So the minimum version becomes 3.2.0 in our case, but it can go up to 4.0.0 (excluding). I remember we got issues with protobuf in the past because suddenly some new version appeared. The
=
forces the crate (and its dependencies) to use that version even if another package could pull a newer version.See this for reference:
https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-path-dependencies