It's not yet idiomatic or good Go code now, though, is it?
IIRC the initial state (1.5) was mostly machine translated code from C to Go.
IIRC the initial state (1.5) was mostly machine translated code from C to Go.
The compilers and low-level toolchain libraries that encode machine instructions have been machine-translated.
The runtime is an example of very good low-level Go code that breaks safety rules. However, it is not a good example of user-level Go code. Note that even though the Go code in the runtime heavily uses unsafe, the runtime is much safer and more stable (we find less bugs) then when it was written in C.
The rest of the runtime probably was already human-written in Go
find -name '*.X' | xargs wc -l in src/runtime saysGo 1.4:
21701 .c 33348 .go 19160 .s
Go 1.7b2: 3340 .c 77597 .go 33827 .s
The assembly growth seems to be attributable to the increased number of supported platforms