You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A detail that increases verbosity of the library API is defining custom flags and options. There are a lot of common flags and options that programs use, such as --verbose and --config. The library should provide many of these so the users don't need to make custom types for them. Here is a proposed implementation:
Instead of defining their own custom types for these common flags and options, they can simply use these predefined types, optionally providing a custom description more relevant to their specific program:
using Parser = CLArgs::Parser<CLArgs::CommonFlags::Verbose,
CLArgs::CommonOptions::Configuration<"My custom description">>;
This would be a very simple improvement to the library, but a very valuable addition.
The text was updated successfully, but these errors were encountered:
A detail that increases verbosity of the library API is defining custom flags and options. There are a lot of common flags and options that programs use, such as
--verbose
and--config
. The library should provide many of these so the users don't need to make custom types for them. Here is a proposed implementation:Instead of defining their own custom types for these common flags and options, they can simply use these predefined types, optionally providing a custom description more relevant to their specific program:
This would be a very simple improvement to the library, but a very valuable addition.
The text was updated successfully, but these errors were encountered: