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 <i...@golang.org> wrote: > On Sat, Jun 22, 2024 at 5:45 PM Will Faught <will.fau...@gmail.com> 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] [-modcache] > [-fuzzcache] [-C dir] [-a] [-p n] [-race] [-msan] [-asan] [-cover] > [-covermode set,count,atomic] [-coverpkg pattern1,pattern2,pattern3] ... > > > > That doesn't seem too useful. > > Agreed, which is why I did not suggest expanding the build flags. I > wrote exactly what I think the output "go clean -h" should be. We > already don't expand the build flags in most of the "go CMD -h" > output. > > Ian > > > > On Sat, Jun 22, 2024 at 5:09 PM Ian Lance Taylor <i...@golang.org> > wrote: > >> > >> On Sat, Jun 22, 2024 at 12:03 AM Will Faught <will.fau...@gmail.com> > 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] [packages] > >> > > >> > -i remove the corresponding installed archive or binary (what > 'go install' would create) > >> > -n print the remove commands it would execute, but not run them > >> > -r apply recursively to all the dependencies of the packages > named by the import paths > >> > -a > >> > force rebuilding of packages that are already up-to-date. > >> > -p n > >> > the number of programs, such as build commands or > >> > test binaries, that can be run in parallel. > >> > The default is GOMAXPROCS, normally the number of CPUs > available. > >> > -race > >> > enable data race detection. > >> > Supported only on linux/amd64, freebsd/amd64, darwin/amd64, > darwin/arm64, windows/amd64, > >> > linux/ppc64le and linux/arm64 (only for 48-bit VMA). > >> > [...] > >> > > >> > Run 'go help clean' for details. > >> > > >> > The clean and build flags would be mixed together and ordered > alphabetically, like flags does. > >> > > >> > Does that look right? > >> > >> No, I was thinking of something different. The current pattern is > >> that "go CMD -h" prints a short summary of the flags. For example > >> > >> > go fmt -h > >> usage: go fmt [-n] [-x] [packages] > >> Run 'go help fmt' for details. > >> > >> This is useful for a quick reminder for how to run the command, and > >> shows people who need more information how to get more information. > >> So I think "go clean -h" should print something like > >> > >> go clean [-i] [-r] [-cache] [-testcache] [-modcache] [-fuzzcache] > >> [build flags] [packages] > >> Run ' go help clean' for details > >> > >> > >> > >> Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAKbcuKj07N2URmmAShzJ26637ztvfmi_dZLpZD_D%2BLH0HXTw8Q%40mail.gmail.com.
