I tried a patch as my first contribution :)
https://github.com/golang/go/issues/68242
Laszlo
Ian Lance Taylor a következőt írta (2024. június 23., vasárnap, 4:01:31
UTC+2):
> 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
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
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
On Mon, Jun 17, 2024 at 10:52 PM Will Faught wrote:
>
> > People who already know what the command does can use that short summary to
> > remind themselves of the available options.
>
> Which options do you mean? My point was that it doesn't document any options.
Oh, sorry, I see what you mean.
> People who already know what the command does can use that short summary
to remind themselves of the available options.
Which options do you mean? My point was that it doesn't document any
options.
On Mon, Jun 17, 2024 at 5:57 PM Ian Lance Taylor wrote:
> On Mon, Jun 17, 2024 at 5:28 PM will.
On Mon, Jun 17, 2024 at 5:28 PM will@gmail.com
wrote:
>
> ❯ go clean -h
> usage: go clean [clean flags] [build flags] [packages]
> Run 'go help clean' for details.
>
> This just tells me to invoke another help command.
>
> The flags package has the opinion that command help should print the do
❯ go clean -h
usage: go clean [clean flags] [build flags] [packages]
Run 'go help clean' for details.
This just tells me to invoke another help command.
The flags package has the opinion that command help should print the doc
for flags. Shouldn't we do that for go clean -h too?
--
You received
12 matches
Mail list logo
