Russ Cox
Does anyone object to accepting this proposal?
How often is this used for something other than a rate-limiting log statement? I'm curious whether it might belong nearer to logging if it's really log-specific.
"some.Times" is a very weird name. There's only one possible symbol you can put in "package some". It's cute but not functional. It seems like we should go back to...
OK it sounds like we are back to ``` type Sometimes struct { First int // if non-zero, the first N calls to Do will run f. Every int //...
Almost no one on earth understands how to write negation regexps correctly, so I would lean toward -skip if we do this.
It sounds like people are generally in favor of adding `-skip` with a default of "matches nothing at all". The `-skip` setting applies after the `-run` setting (which already defaults...
> 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, at least interactively,...
@magical, more magic in -run is not a good idea. The slash was not great either but is done.
`-list` already applies to everything - tests, benchmarks, examples - so I think it's probably OK to have `-skip` do the same (apply to benchmarks; tests and examples were already...
Based on the discussion, this seems like a **likely accept**.