How do you manage multiple related Rust crates as a single unit?
Tests Cargo workspaces for multi-crate Rust projects. Strong answers cite the [workspace] section, shared Cargo.lock, unified target directory, inherited metadata, and workspace-wide commands.
This tests Cargo workspace fluency for scaling Rust monorepos. A strong answer names the [workspace] section in a root Cargo.toml or virtual manifest, then lists four benefits: a single Cargo.lock unifies dependency versions; a shared target directory saves disk and rebuild time; workspace.package and workspace.dependencies centralize metadata; and commands like cargo check --workspace run across all members. Red flag: manual path dependencies, git submodules, or forgetting that [patch] and [profile] are root-only.
Read the original → doc.rust-lang.org
- #rust
- #cargo
- #workspaces
- #monorepo
- #dependency-management
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.