Remove Cargo.lock about sandbox HOT 2 CLOSED

When you specify foo = "1.3" in your Cargo.toml, that means "any version of dependency foo 1.3.0 or higher". If Cargo.lock is not present, then cargo will choose the latest version available, and set that in Cargo.lock. If Cargo.lock is present, then cargo will choose exactly the version listed in there, regardless of what the newest compatible version available actually is.

That's the whole point of the Cargo.lock file - to explicitly pin your dependencies to specific versions, so that the build can be more reproducible. Generally, applications track their Cargo.lock with git; only libraries do not.

See https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html for more info.

from sandbox.

You learn something new every day I guess :)

from sandbox.