Chris Hines
Chris Hines
My prototype is in #73. I have submitted it as a Draft since it is merely a suggestion at this point and I have made no effort to update any...
> this seems easily solved by using fully-qualified ShortUsage strings for each subcommand Indeed, that is a solution, but as a programmer I would rather not have to couple subcommand...
Thanks for clarifying the design goals. When a global flag is duplicated in all subcommands how do you typically indicate to the end user which flags are global and which...
I have almost moved some subtests into their own top level test function on a few occasions exactly because there was not a good way to skip some subset of...
A way to skip benchmarks would be welcome as well. The `-run` and `-bench` flags have different defaults. In my experience `go test -run=^$ -bench=.` is pretty common today, but...
> > The -run and -bench flags have different defaults. In my experience go test -run=^$ -bench=. is pretty common today > > FWIW this is usually a bad idea,...
No objection here.
This is an interesting idea. I would like to think about this a bit before deciding to merge it. In the mean time, would you kindly target this PR to...
Thanks for retargeting. I've taken a closer look at this PR and run the benchmarks. I'm persuaded that this would be a valuable addition, but I see some things we...
@lukseven We may be able to get the performance gains you want without adding new functions to the API. This package used to be more efficient prior to the introduction...