Via godoc command or the web interface it provides.
In most cases, examples look equally good in both interfaces. However, in some cases, there may be two alternative ways to write an example, such that one of them looks better inside source code, and the other looks better in the godoc interface.
My understanding is that it's better to prioritize the godoc interface over the source code, since most people will be reading examples via godoc (be it locally, or via https://godoc.org, or https://golang.org/pkg/). If that is not correct, the rest of this issue is not valid.
I found that there are 5 examples in encoding/json package that have raw strings with indentation which is suboptimal when seen via the godoc interface.
The existing example for Decoder.Decode (Stream) had excessive
indentation in the godoc interface for the const jsonStream,
making it hard to read. This fixes the indentation in the
example_test.go to improve the readability in godoc.
Reviewed-by: Dmitri Shuralyov <email@example.com>
Reviewed-by: Brad Fitzpatrick <firstname.lastname@example.org>