On Fri, Jan 19, 2018 at 10:07 AM, Ian Lance Taylor <i...@golang.org> wrote: > Sounds like a good approach. Or I'm also open to someone writing the > necessary code for golang.org.
I just started this approach simply serving static html files: https://golangdoc.github.io/pkg/1.10beta2/ https://golangdoc.github.io/pkg/1.8.5/ https://golangdoc.github.io/pkg/1.8/ https://golangdoc.github.io/pkg/1.6/ Only the doc under pkg/ works so far, not any src/ code yet (some generated html for src/ are too big, I'm not sure how to handle efficiently), for my own use case, the pkg/ doc is most often looked up as reference; On Friday, January 19, 2018 at 3:54:34 PM UTC-8, Florin Pățan wrote: > I think this would further encourage people to be lazy and not upgrade to > newer Go versions. Development within corporate has a nature of being conservative; you can't simply force everyone to upgrade As the Golang grows to age 10+; at some point, you will have to handle the historic versions; I still hope this can be handled by official golang.org/ At least so far, I can simply share by a single link to friends of these links, and these are permanent links, public to Google search https://golangdoc.github.io/pkg/1.10beta2/strings/index.html#Builder (the one added in Go1.10) https://golangdoc.github.io/pkg/1.10beta2/sync.html#Map (this one added in Go1.9) https://golangdoc.github.io/pkg/1.8/sort/index.html#Slice (this one added in Go1.8) I am not subscribing the whole golang-nuts@ ; so please copy me if you want me to report issues to me. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
