On Sat, Jun 22, 2024, 6:21 PM Will Faught wrote:
> I see. That doesn't seem very useful to me, so I won't be making a patch
> for it. Thanks anyways.
>
No worries. We're trying to strike a balance between a reminder and full
documentation. I don't think we need two different ways to get the fu
I see. That doesn't seem very useful to me, so I won't be making a patch
for it. Thanks anyways.
On Sat, Jun 22, 2024 at 5:48 PM Ian Lance Taylor wrote:
> On Sat, Jun 22, 2024 at 5:45 PM Will Faught wrote:
> >
> > Ian,refer>
> > I see. I'm concerned that approach wouldn't scale to the number of
On Sat, Jun 22, 2024 at 5:45 PM Will Faught wrote:
>
> Ian,refer>
> I see. I'm concerned that approach wouldn't scale to the number of clean and
> build flags there are. I count 8 clean flags and 10+ build flags. That would
> look like:
>
> > go clean [-i] [-n] [-r] [-x] [-cache] [-testcache] [-
Ian,
I see. I'm concerned that approach wouldn't scale to the number of clean
and build flags there are. I count 8 clean flags and 10+ build flags. That
would look like:
> go clean [-i] [-n] [-r] [-x] [-cache] [-testcache] [-modcache]
[-fuzzcache] [-C dir] [-a] [-p n] [-race] [-msan] [-asan] [-co
On Sat, Jun 22, 2024 at 12:03 AM Will Faught wrote:
>
> Sure thing.
>
> Just want to make sure we're on the same page. We would be changing the clean
> command help message to document its clean and build flags like the flags
> package does:
>
> usage: go clean [clean flags] [build flags] [packa
Thanks for point it out Brian. I must of had some background interference. I
re-ran the tests, Go was the same, Java is
Benchmark Mode Cnt ScoreError Units
TestJavaDispatch.TestArrayDispatch avgt9 4367.196 ± 50.227 ns/op
TestJavaDispatch.TestDispatch
Will,
The help system for go commands is provided by the help subcommand.
$ go help
For example,
$ go test -h
usage: go test [build/test flags] [packages] [build/test flags & test
binary flags]
Run 'go help test' and 'go help testflag' for details.
$
If you want to change
Sure thing.
Just want to make sure we're on the same page. We would be changing the
clean command help message to document its clean and build flags like the
flags package does:
usage: go clean [clean flags] [build flags] [packages]
-iremove the corresponding installed archive or binary (w
