iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Build a Rust command-line application by creating a binary project, reading its arguments, and running it through Cargo. Use Cargo’s release profile when preparing an optimized production artifact—but measure your own workload before claiming a performance gain. The official Rust learning example provides a simple starting point for the project and argument flow.
Start a Rust binary project
Use Cargo to create a new binary project:
cargo new minigrep
cd minigrepThis creates a project named minigrep. The Rust Book uses that name in its command-line example, which accepts a search query and a file path.
Pass arguments to the program
In the Rust Book’s introductory example, the program reads command-line arguments with Rust’s standard-library std::env::args. Run the program with Cargo like this:
cargo run -- searchstring example-filename.txtThe two hyphens are a separator: arguments after -- go to the binary, while options before it are passed to Cargo. This distinction matters when your program’s arguments could otherwise be interpreted as Cargo options. See The Rust Book’s command-line argument example and Cargo’s documentation for cargo run.
#1 Best Overall
std::env::args is a useful foundation for following the learning example and understanding how a program receives arguments. As the command interface grows, choose an argument-parsing approach that fits its needs; parsing needs vary with the number of options, validation rules, and desired user experience.
Build an optimized artifact with Cargo
For a release build, run:
cargo build --releaseCargo’s release profile is intended for optimized artifacts used in releases and production. You can also ask cargo run to run the optimized artifact with --release:
Rank #2
cargo run --release -- searchstring example-filename.txtHere, the first --release is a Cargo option; the second -- separates Cargo’s options from the binary’s arguments. Cargo documents the release profile as an optimization-oriented build configuration, not a guarantee of a particular runtime, startup, or binary-size improvement. Results depend on the application and workload. For performance claims, benchmark the actual program under representative conditions rather than assuming a fixed speedup. See Cargo’s profile documentation.
Choose the next level of CLI structure
A small learning program can begin with the standard library’s argument handling. A more involved tool may need a dedicated argument parser, layered configuration, or careful handling of input and output streams. Treat these as design decisions driven by the command’s requirements, not as prerequisites for every Rust CLI.
Rank #3
A retailer listing for a related Rust systems programming book describes a project involving a high-performance command-line tool and lists clap argument parsing, layered configuration, and efficient I/O streams among its topics. Those are claims in the retailer’s description, not an independent assessment of the book’s contents or a benchmark of the techniques.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Related reading: a different Rust book title
If you are looking for a Rust CLI programming book, Bookshop.org lists Mastering Systems Programming with Rust: A hands-on guide to building High-Performance CLIs, System Daemons, and Low-Level Libraries by Samuel E. Barnard. It is related further reading, not a book titled Mastering Rust: Build a High-Performance CLI Application. The listing gives a June 12, 2025 publication date, 140 pages, and ISBN 9798287780937. Its description mentions clap, layered configuration, and I/O streams. View the Bookshop.org listing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
