The "Try Go" element on the golang.org homepage has two different Hello world, one of which is not gofmt-ed.
When you load golang.org for the first time, the "Try Go" element on the right look like this:
The "Open in Playground" element links to https://play.golang.org/p/MbPUiI4y-IE, which contains a non-gofmt-ed Hello world (it uses 2 spaces to indent the fmt line).
If you use the selector below to display another code snippet (say, Concurrent Pi), and then you re-select Hello world, the Hello that is displayed looks like this:
Note how this is a different Hello world (gofmt-ed, and the comment at the top is missing). The "Open in Playground" element links to a different program (https://play.golang.org/p/7vin2BK8_A6).
We should probably settle on one Hello world (gofmt-ed).
If we want to keep two (one with the "// You can edit this code!" comment at the top, and one without), we should at least gofmt the default one. It looks bad to have a non-gofmt-ed program on the homepage.
The "Try Go" element on the golang.org homepage has two different Hello world, one of which is not gofmt-ed.
When you load golang.org for the first time, the "Try Go" element on the right look like this:
The "Open in Playground" element links to https://play.golang.org/p/MbPUiI4y-IE, which contains a non-gofmt-ed Hello world (it uses 2 spaces to indent the
fmtline).If you use the selector below to display another code snippet (say, Concurrent Pi), and then you re-select Hello world, the Hello that is displayed looks like this:
Note how this is a different Hello world (gofmt-ed, and the comment at the top is missing). The "Open in Playground" element links to a different program (https://play.golang.org/p/7vin2BK8_A6).
We should probably settle on one Hello world (gofmt-ed).
If we want to keep two (one with the "// You can edit this code!" comment at the top, and one without), we should at least gofmt the default one. It looks bad to have a non-gofmt-ed program on the homepage.