Workspace

As explained in Refactoring to Rust

A Cargo workspace is a collection of related Rust packages that share a lockfile and build output directory.

How Refactoring to Rust covers it

How deep it goes

Demonstrates creation, membership configuration, path dependencies, target configuration, building, and execution.

Examples

Uses paper_search and paper_search_lib to fetch, parse, format, build, and run search results as Wasm.

What you can do after

Builds and runs a workspace containing a Wasm binary that calls reusable library code.

How it connects

Connects Cargo manifests, Rust libraries, binaries, path dependencies, WebAssembly, WASI, and WasmEdge.

liveBookmanning.com

Read Refactoring to Rust on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Rust Servers, Services, and AppsA Cargo workspace is a set of related Rust packages managed and built together by Cargo.

Compare how 2 books explain workspace →

Related concepts

• crateuses · A crate is Rust’s unit of compilation and distribution, containing source code and metadata for a library or executable.
• cargo.tomlconfigured by · Cargo.toml is a TOML-formatted Rust package manifest declaring project metadata, dependencies, targets, and build configuration.
• lock fileuses · A lock file records resolved dependency versions and related metadata so a package manager can reproduce a project's dependency installation.
• applicationhas part · An application is a software program or system that performs tasks or provides functionality for users or other software systems.
• dependencyaddresses · A software dependency is a component, resource, or prerequisite on which another software component or operation relies to function or proceed.

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