News for hackers. Stuff that matters.

A comment on Tokio 1.0 – async runtime for Rust. Parent comment

Re:Tokio 1.0 – async runtime for Rust by zozbot234 on Friday December 25, 2020 @10:11AM (#25536870)
> Yes. Rust encourages version pinning.

Rust makes version pinning feasible, e.g. by allowing multiple versions of the same package in a build (not all module systems have this feature!) but doesn't encourage it. You've identified a problem with using 0.x.y-versioned packages as dependencies (which means de-facto opting out of semver), but that's not a problem with Rust specifically; it could occur in any language.

[ Parent | on HN ]
Re:Tokio 1.0 – async runtime for Rust by steveklabnik on Friday December 25, 2020 @10:54AM (#25537119)
To be clear, the default semantics are ^, not =. So even if you put 1.2.3 in your Cargo.toml, you may get 1.3.0, you just won’t get 2.0.0.
[ Parent | on HN ]
Re:Tokio 1.0 – async runtime for Rust by pjmlp on Saturday December 26, 2020 @08:18AM (#25543267)
Which might lead to the same outcome anyway as there is nothing that prevents those version numbers to actually mean anything.

It is up to the library authors to uphold its semantics.

[ Parent | on HN ]