Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/tools/cmd/godoc: HTML formatting doesn't make association between comments and code clear #16728

Closed
mkrautz opened this issue Aug 16, 2016 · 5 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@mkrautz
Copy link
Contributor

mkrautz commented Aug 16, 2016

screen shot 2016-08-16 at 10 51 42

@mkrautz
Copy link
Contributor Author

mkrautz commented Aug 16, 2016

Hmm. I now see that that's just the way godoc does things.

I was just confused by the paragraph in the context of the "Variables" section.

It's not clear whether it documents what's above it (the errors), or the new context variables below it. Perhaps because neither the first errors section nor the new context section has a comment attached to them.

@bradfitz bradfitz changed the title net/http: Go 1.7 docs for net/http has out-of-place "Errors used by the HTTP server" paragraph x/tools/cmd/godoc: HTML formatting doesn't make association between comments and code clear Aug 16, 2016
@bradfitz bradfitz added this to the Go1.8Maybe milestone Aug 16, 2016
@bradfitz
Copy link
Contributor

/cc @broady

@quentinmit quentinmit added the NeedsFix The path to resolution is known, but the work has not been done. label Oct 10, 2016
@rsc rsc modified the milestones: Go1.9, Go1.8Maybe Oct 21, 2016
@gopherbot
Copy link

CL https://golang.org/cl/32153 mentions this issue.

@gopherbot
Copy link

CL https://golang.org/cl/32154 mentions this issue.

@gopherbot
Copy link

CL https://golang.org/cl/33279 mentions this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

No branches or pull requests

5 participants