The go doc command lists these under global functions, whereas godoc.org and pkg.go.dev was listing them under the base type they return for example ParseAcceptLang was listed under Tag. The difference between go doc and the web based documentation confused me. Shouldn't the output of both ways be comparable?
On Monday, June 29, 2020 at 2:11:31 PM UTC+2, Jens-Uwe Mager wrote: > > I am having problems that some of the docs I am looking at show only one > single line of exported global functions. Example here > > https://godoc.org/golang.org/x/text/language#pkg-index > > Running this command: > > go doc golang.org/x/text/language > > I get much more exported global functions: > > ... > func CompactIndex(t Tag) (index int, exact bool) > func Compose(part ...interface{}) (t Tag, err error) > func EncodeM49(r int) (Region, error) > func Parse(s string) (t Tag, err error) > func ParseAcceptLanguage(s string) (tag []Tag, q []float32, err error) > func ParseBase(s string) (Base, error) > func ParseExtension(s string) (e Extension, err error) > func ParseRegion(s string) (Region, error) > func ParseScript(s string) (Script, error) > func ParseVariant(s string) (Variant, error) > ... > > any preference I can set at godoc.org (or pkg.go.dev) to see all > available global functions? Or is this a bug? > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/b19c7235-6092-4e61-87e1-4ffa0ffa649ao%40googlegroups.com.
