Command-line flags are documented in the rustc book. All stable flags should be documented there. Unstable flags should be documented in the unstable book.
See the forge guide for new options for details on the procedure for adding a new command-line argument.
- Flags should be orthogonal to each other. For example, if we'd have a
json-emitting variant of multiple actions
bar, an additional
--jsonflag is better than adding
- Avoid flags with the
no-prefix. Instead, use the
parse_boolfunction, such as
- Consider the behavior if the flag is passed multiple times. In some
situations, the values should be accumulated (in order!). In other
situations, subsequent flags should override previous flags (for example,
the lint-level flags). And some flags (like
-o) should generate an error if it is too ambiguous what multiple flags would mean.
- Always give options a long descriptive name, if only for more understandable compiler scripts.
--verboseflag is for adding verbose information to
rustcoutput. For example, using it with the
--versionflag gives information about the hashes of the compiler code.
- Experimental flags and options must be guarded behind the