But without godoc there's still to sensible way to check the documentation
before committing and pushing the commits. And running pkgdev yourself is a
complete mess, not least due to it enforcing the use of an additional
proxy, TLS woes, et cetera.
On Saturday, June 25, 2022 at 10:22:47 PM UTC+
Maybe it's clearer if you look at what's happening like this
https://go.dev/play/p/jAia9OPJfbY
The arguments to defer are evaluated immediately, but the execution only
happens later
- sean
On Sat, Jun 25, 2022, 21:40 Lee Chou wrote:
> Hello,
>
> https://go.dev/play/p/J1tVplkIrjt
>
> why o1.Ref
Hello,
https://go.dev/play/p/J1tVplkIrjt
why o1.Ref print `2` but p1.Ref print `1` ?
why o1.Ref print `2` but o2.NonRef print `3` ? it's so confused.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop rec
I believe the answer is using godoc
That would be a correct link if you used pkgsite
godoc is deprecated as of https://github.com/golang/go/issues/49212
- sean
On Sat, Jun 25, 2022, 20:54 TheDiveO wrote:
> Using go1.19beta1 I installed godoc using "go1.19beta1 install
> golang.org/x/tools/cmd/
Using go1.19beta1 I installed godoc using "go1.19beta1 install
golang.org/x/tools/cmd/godoc@latest". Then I tried to create a "Doc link"
as per https://tip.golang.org/doc/comment, section heading "Doc link",
running a godoc server on localhost:6060.
In package documentation for github.com/thedi
