Block a user
CLI execution shouldn't call subcommands recursively
Produce useful error messages on failure
consider: forbid ordered arguments on commands with subcommands
One possible option for making this compile-time behavior would be to remove addSubcommand from the parser interface and add a method to the generic parser instance to easily get a heap-allocated…
Improve ergonomics of early-exit flags on commands that require subcommands
consider: forbid ordered arguments on commands with subcommands
Improve typo subcommand error message
Fix the really stupid way the user context is handled.
Add fencing mechanism for disabling help output auto line wrapping