-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/doc: doc links in doc of a method in an interface are not expanded #59728
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
Comments
CL 486815 (in which I add godoc links to |
cc @rsc @griesemer |
This is related to the discussion in #56592. The way that cmd/doc works for aggregate types is that it calls into go/format to print those types. That does the right thing for internal comments. But it does not format doc comments. https://go.dev/cl/483055 applied a workaround to address one aspect of this. Perhaps to really get this right we need to change go/format, or we need to change cmd/doc to not use go/format. Neither seems particularly simple. |
Probably related to, or a dup of, #56004. |
@willfaught #56004 mentions a |
Change https://go.dev/cl/501115 mentions this issue: |
This clarifies the ambiguity of the TODO word as raised in #56625. Also links the introduction text to each function. Note: linking from Context methods documentation is blocked for now by #59728. Change-Id: Ie6080bd8dee3a652436b0875ddc5f452287c9493 Reviewed-on: https://go-review.googlesource.com/c/go/+/501115 Reviewed-by: Ian Lance Taylor <iant@google.com> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com> Run-TryBot: Ian Lance Taylor <iant@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
What version of Go are you using (
go version
)?What did you do?
What did you expect to see?
What did you see instead?
[Foo]
is not expanded in the comment before theBaz
method.Impact
Doc links are very useful to document packages that rely heavily on interfaces (ex:
database/sql/driver
) but this issue blocks the full potential of doc links. (also #54033).The text was updated successfully, but these errors were encountered: