clap/examples/tutorial_builder/03_03_positional.rs

// Note: this requires the `cargo` feature

use clap::{arg, command};

fn main() {
    let matches = command!().arg(arg!([NAME])).get_matches();

    println!("NAME: {:?}", matches.get_one::<String>("NAME"));
}
docs: Annotate more places with required features 2022-03-03 18:32:29 +00:00			// Note: this requires the `cargo` feature

docs: Update to new `command!` macro 2022-02-15 14:33:38 +00:00			`use clap::{arg, command};`
docs: Re-work examples This creates distinct tutorial examples from complex feature examples (more how-tos). Both sets are getting builder / derive versions (at least the critical ones). 2021-11-30 18:30:19 +00:00
			`fn main() {`
docs: Update to new `command!` macro 2022-02-15 14:33:38 +00:00			`let matches = command!().arg(arg!([NAME])).get_matches();`
docs: Re-work examples This creates distinct tutorial examples from complex feature examples (more how-tos). Both sets are getting builder / derive versions (at least the critical ones). 2021-11-30 18:30:19 +00:00
fix(parser): Simplify the common getter API Clap has focused on reporting development errors through assertions rather than mixing user errors with development errors. Sometimes, developers need to handle things more flexibly so included in #3732 was the reporting of value accessor failures as internal errors with a distinct type. I've been going back and forth on whether the extra error pessimises the usability in the common case vs dealing with the proliferation of different function combinations. In working on deprecating the `value_of` functions, I decided that it was going to be worth duplicating so long as we can keep the documentation focused. 2022-05-25 15:46:42 +00:00			`println!("NAME: {:?}", matches.get_one::<String>("NAME"));`
docs: Re-work examples This creates distinct tutorial examples from complex feature examples (more how-tos). Both sets are getting builder / derive versions (at least the critical ones). 2021-11-30 18:30:19 +00:00			`}`