forked from daa84/neovim-gtk
-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix versioning of dependencies in Cargo.toml (properly, this time)
As @jacobmishka pointed out [here](3fd8c5a#commitcomment-57920421), it appears that I've misunderstood how Cargo's versioning works, but I think I get it now! (hopefully…)
- Loading branch information
Showing
1 changed file
with
40 additions
and
40 deletions.
There are no files selected for viewing
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
95a92d9
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.
Ha, these are completely equivalent, so no harm. Mainly I was just pointing out that the minor versions that were removed last time meant that a small bit of information was lost.
For example,
clap
used to be2.33
, meaning that anything above 2.33 but below 3.0 would work (for example, if you know that 2.32 didn't have a feature that 2.33 had that we're relying on). Now, with2.0
, anything 2-3 will work, meaning that in the hypothetical situation where 2.32 wouldn't actually work then we're misrepresenting our dependencies.Again, none of this should really matter in practice, I was just pointing it out because coming from JavaScript I was also confused about Cargo's dependency resolution at first for a while.