You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked the documentation for cmd/vet, by both running go doc cmd/vet and visiting https://golang.org/cmd/vet/.
What did you expect to see?
I expected to see a heading and an accompanying table of contents entry for each of the options listed in go tool vet -h.
What did you see instead?
In both my local docs output and the online docs, there appear to be a number of missing headings. This makes both the table of contents and the document body rather confusing.
For example, there's no heading for the -tests flag; the docs are included under the section on copying locks, which doesn't make much sense.
Even more confusing, the section on struct tags doesn't contain any information about struct tags at all. Instead, it contains the documentation for -rangeloops.
If this is indeed a bug (and not just an organizational scheme I'm not grokking), I'm happy to open a CL to fix it.
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?go version go1.7.4 darwin/amd64
What operating system and processor architecture are you using (
go env
)?What did you do?
I checked the documentation for
cmd/vet
, by both runninggo doc cmd/vet
and visiting https://golang.org/cmd/vet/.What did you expect to see?
I expected to see a heading and an accompanying table of contents entry for each of the options listed in
go tool vet -h
.What did you see instead?
In both my local docs output and the online docs, there appear to be a number of missing headings. This makes both the table of contents and the document body rather confusing.
For example, there's no heading for the
-tests
flag; the docs are included under the section on copying locks, which doesn't make much sense.Even more confusing, the section on struct tags doesn't contain any information about struct tags at all. Instead, it contains the documentation for
-rangeloops
.If this is indeed a bug (and not just an organizational scheme I'm not grokking), I'm happy to open a CL to fix it.
The text was updated successfully, but these errors were encountered: