Cargo Crates.io
Comprehension
Compilation optimization options
// Filename: Cargo.toml // opt-level controls optimization from 0 to 3; higher values increase compile time and runtime efficiency [profile.dev] opt-level = 0 [profile.release] opt-level = 3Doc String
//! # My Crate //! //! `my_crate` is a collection of utilities to make performing certain //! calculations more convenient. /// Adds one to the number given. /// /// # Examples /// /// ``` /// let arg = 5; /// let answer = my_crate::add_one(arg); /// /// assert_eq!(6, answer); /// ``` pub fn add_one(x: i32) -> i32 { x + 1 }Use
cargo docto generate documentation//!is generally used to document an entire crate or module, while///is generally used for functions

Workspaces
A workspace is a set of packages that share the same Cargo.lock and output directory
Can be used to manage multiple modules with the same purpose
They share the same Cargo.lock and output directory
Other
cargo installinstalls and runs binary crates
Origin
https://doc.rust-lang.org/book/ch14-00-more-about-cargo.html
…
Extending Cargo with Custom Commands
Cargo is designed so you can extend it with new subcommands without having to modify Cargo. If a binary in your $PATH is named cargo-something, you can run it as if it was a Cargo subcommand by running cargo something. Custom commands like this are also listed when you run cargo --list. Being able to use cargo install to install extensions and then run them just like the built-in Cargo tools is a super convenient benefit of Cargo’s design!
Summary
Sharing code with Cargo and crates.io is part of what makes the Rust ecosystem useful for many different tasks. Rust’s standard library is small and stable, but crates are easy to share, use, and improve on a timeline different from that of the language. Don’t be shy about sharing code that’s useful to you on crates.io ; it’s likely that it will be useful to someone else as well!