Over time, we amassed a fair amount of boilerplate even though we are already using a proc-macro driven argument parser, structopt.
For clarification, this originates from the requirement of supporting shared and distinct options per subcommand. Maybe I don't use structopt's full potential yet or it simply cannot handle it and we are forced to go back to the procedural API of clap.
We also need to design the basic options our CLI should currently understand: Selecting between the engines TWI and BCI, perma-unstable flags, etc.
Over time, we amassed a fair amount of boilerplate even though we are already using a proc-macro driven argument parser,
structopt
. For clarification, this originates from the requirement of supporting shared and distinct options per subcommand. Maybe I don't usestructopt
's full potential yet or it simply cannot handle it and we are forced to go back to the procedural API ofclap
.We also need to design the basic options our CLI should currently understand: Selecting between the engines TWI and BCI, perma-unstable flags, etc.