7 ms·
Yeah I was referring to the reference toolchain. Not very deep in the go ecosystem, but I presume it's the one which has most use? Regarding the bootstrapping
by est31 6y ago
Yeah I was referring to the reference toolchain. Not very deep in the go ecosystem, but I presume it's the one which has most use?
Regarding the bootstrapping point, rustc was bootstrapped via a "rustboot" compiler written in ocaml. Doesn't make the rust compiler any less rust now, as it compiles itself nowadays (to be precise, version N compiles version N+1, and also supports compiling version N, at least for bootstrap purposes).
- pjmlp 6y agoMy point was more to make it clear that language != implementation, hence the various ones for Go.
- est31 6y agoIndeed, those two aren't the same concepts, but the person I replied to said "It finally possible to make Linux binaries in a high level language not involving anything written in C at build-time or run-time", so mainly referring to the possibility instead of all implementations being that way. For go I didn't want to go into further detail then as I assumed the "default go experience" entails only the official Go toolchain.
- pjmlp 6y agoFair enough.