How deeply does Code Like a Pro in Rust cover lock file?

Defines file contents and gives version-control and update guidance, without detailing the lock file format.

Lock file

Cargo.lock is Cargo’s lock file that records exact package dependency versions and integrity checksums.

Cargo.lock records the resolved versions of direct and indirect package dependencies, plus checksums used to verify their integrity. Cargo.toml declares dependency requirements; the lock file records the packages selected under those requirements. section 2.2.1 section 2.2

Choose version-control treatment by project type:

Applications: commit Cargo.lock alongside Cargo.toml to help keep published releases consistent if third-party libraries change. section 2.2.1
Libraries: leave Cargo.lock out of version control so downstream packages can update indirect dependencies as needed; with Git, add it to .gitignore. section 2.2.1

Run cargo update to refresh Cargo.lock to the newest available crates permitted by the dependency specifications. This differs from pinning a version with an exact requirement in Cargo.toml: the requirement controls which versions are eligible. section 2.2

Listing 2.1 A minimal Cargo.toml

[package]
name = "simple-project"
version = "0.1.0"
authors = ["Brenden Matthews <brenden@brndn.io>"]
edition = "2018"

[dependencies]
rand = "0.8"

The rand = "0.8" entry is a Cargo.toml dependency requirement, not a record of every resolved package version. section 2.2

Workspace members share one top-level Cargo.lock and its resolved dependency tree. Keep member dependencies declared in Cargo.toml; workspace membership does not replace dependency declarations. section 2.10

How Code Like a Pro in Rust covers it

liveBook manning.com

Read Code Like a Pro in Rust on liveBook Get the book at manning.com

Related concepts

dependencyconfigures · A software dependency is a component, resource, or prerequisite on which another software component or operation relies to function or proceed.
dependency managementused by · Dependency management is the practice of declaring, resolving, versioning, obtaining, updating, and controlling the software components required by a project.
npmused by · npm is a package-management system for JavaScript, comprising a command-line client and an online registry for discovering, installing, and publishing packages.
.gitignoreconfigured by · .gitignore is a Git configuration file containing patterns that specify files and directories Git should exclude from version-control tracking.

This explainer was generated by Manning's knowledge graph from the text of Code Like a Pro in Rust. The section links point to the parts of the book it draws on.