The go doc command lists these under global functions, whereas 
and 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 

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
> Running this command:
> go doc
> 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 (or 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 view this discussion on the web visit

Reply via email to