3 ms·
I gave an example a bit further up, here [1]. [1] https://news.ycombinator.com/item?id=22240223 https://news.ycombinator.com/item?id=22240223
by calcifer 7y ago
I gave an example a bit further up, here [1].
[1] https://news.ycombinator.com/item?id=22240223 https://news.ycombinator.com/item?id=22240223
- _ph_ 7y agoBut this isn't a contradiction to the statement, that Go is implemented in Go. If you look at the sources of the Go implementation, the source code is 99% Go, with a few assembly functions (most for optimizations not performed by the compiler) and no other programming language used.
- calcifer 7y agoThat's not correct. The implementation of "make", for example, looks like Go but isn't - it relies on internal details of the gc compiler that isn't part of the spec [1]. That's why a Go user can't implement "make" in Go. [1] https://golang.org/ref/spec https://golang.org/ref/spec
- _ph_ 7y agoIn which language do you think is "make" implemented?
- scott_s 7y agoIf I may interject: I believe you are both trying to make orthogonal points. calcifer's is trying to say that some features of Go are compiler intrinsics, and cannot be implemented as a library. You are making a different point, which is that those intrinsics are implemented in Go, the host language. Both statement can be true at the same time, but I agree that the terms were not used entirely accurately, causing confusion.