Aram Hăvărneanu
unread,Aug 19, 2014, 9:55:53 AM8/19/14Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Russ Cox, Andrew Gerrand, Konstantin Kulikov, golang-dev
I apologise for asking something you said not to ask in your first
post, but I must.
If there are no plans to serve subrepo documentation, what's the point
of x in the import paths? Specifically, why
golang.org/x/foo instead
of the simpler
golang.org/foo?
The potential name clash in the documentation is avoided by not
presenting subrepo documentation at all (e.g.
golang.org/net prints
net docs, not
go.net docs), and the import paths are unique (e.g. net
is the stdlib net,
golang.org/net is
go.net).
I agree there's a subtle confusion:
golang.org/net will show stdlib
documentation and at the same time it must print
go.net meta tags. Is
that the reason for x?
--
Aram Hăvărneanu