It would be nice if godoc could automatically link text that refers to extant packages.
Comment From: adg
Labels changed: added godoc.
Comment From: gopherbot
Yes please This is silly that its not there.. I cannot even create a summary text and link directly to types and functions etc. Also missing is basic fomratting eg * for bullets and == for headings ==
Comment From: griesemer
This request is somewhat underspecified to act upon. Questions to be answered: 1) What godoc text? Comments that shows up in documentation? Any godoc text (probably not). Something else? 2) When does a package exist? When it's in the std lib? Somewhere else? There already is a mechanism to highlight individual words in documentation comments, for instance to connect the documentation to parameter names in the documented function or method. That machinery is not used yet. It could be modified to do a bit more.
Comment From: adg
1) Anything that we search for and linkify "http://example.com". 2) When godoc lists it in /pkg/.
Comment From: gopherbot
Maybe a textual way to say "expand this symbol"? Something like: `!`io.Reader`
Comment From: 4ad
No magic syntax. Just plain text.
Comment From: gopherbot
Why not markdown? It's conrete, easy-to-read and well-known. http://daringfireball.net/projects/markdown/syntax
Comment From: adg
It has been debated before. The conclusion is that we will not include any kind of special syntax in godoc comments. The consensus is that they should read just like regular comments, and require very little understanding of godoc's mechanisms to write correctly.
Comment From: adg
Issue #5852 has been merged into this issue.
Comment From: adg
Issue #6207 has been merged into this issue.
Comment From: rsc
Labels changed: added repo-tools.
Comment From: rsc
Adding Release=None to all Priority=Someday bugs.
Labels changed: added release-none.
Comment From: kegsay
I think this specific feature request is "in the spirit of" the simple GoDoc style requirements in the same way that http://
links are. They are regular comments that make sense on their own.
My use case is to be able to have well-documented package overviews which then link off to sub-packages for further reading. There is a concern that this could feature-creep (e.g. linking to a specific definition in a given package) but the simple case of linking to a package only seems pretty uncontroversial to me.
Comment From: griesemer
Marking this 1.13 so it gets some visibility.
Comment From: seankhliao
documentation links are available for modern doc systems https://go.dev/doc/comment#links
Comment From: gopherbot
Change https://go.dev/cl/681675 mentions this issue: crypto/internal/boring: upgrade module to fips-2023042800 / CMVP #4953