3 ms·

Why would uno not work on 1.4?

• steveklabnik 12y ago
  When you declare an x.y.z dependency, tools that use SemVer (like Bundler, which is the biggest influence on Cargo) assume x.y.(>z). So, a 1.4.12 dependency says "Anything greater than 1.4.12, but less than 1.5.0." When you declare an x.y dependency, tools that use SemVer assumes x.(>y). So, a 1.4 dependency says "Anything greater than 1.4.anything, but less than 2.anything.anything". This is assuming the ~> operator, if it was =, it would ONLY be 1.14.2, which is even more restrictive. The project _should_ work, which is why Cargo is using this modified version of ~>.