Context: I wrote most of the stdlib docs

the fmt docs are... not ideal. That said, there's a lot there, and it's all useful, but it's just tough. Frankly, I just punted on improving them, and haven't taken the time to do so in the years since.

It seems like enough people find their way around them. Refinement might make them easier for people like me with less experience navigating language documentation, but that might come at the expense of developing the language. Priorities are important. Especially since Rust doesn't have Google's resources.

In terms of content, they seem to be on par, and I think it's safe to say that's true for both stdlibs.

Across the ecosystem (and particularly the third-party culture of documentation) is much more important; in my own experience playing with both languages, I tended to encounter more useless 1-line descriptions in golang than I did in Rust.

Also golang struct descriptions always seem to be a bit lackluster..

But I can't point to any particular lib at the moment though.

Even if it's not the author's favorite piece of doc, this is still a pretty good example of why I like rust docs. The rust version has :

- syntax highlighting

- a quick example of the feature