4 ms·
Can you clarify further? Otherwise this seems like a shallow dismissal, which is against our HN community guidelines, and makes for uninteresting discussion.
by metadat 5y ago
Can you clarify further? Otherwise this seems like a shallow dismissal, which is against our HN community guidelines, and makes for uninteresting discussion.
- alice-i-cecile 5y agoProgramming languages have a large amount of irreducible complexity. A page long spec for a language more complex than Brainfuck cannot represent the critical distinctions correctly. Without that clarity, you end up with incompatible, spec-compliant implementations. This is a disaster, and so below a certain point relative to language complexity a shorter spec is simply wrong.
- metadat 5y agoAre there nasty divergences between official go and cgo?
- josephcsible 5y agoAs it turns out, Go's spec is 105 pages long, not just one as was claimed upthread: https://go.dev/ref/spec https://go.dev/ref/spec So the answer to your question is "not that I know of", but that's not evidence that a one-page spec is workable after all.
- randomdata 5y ago> Without that clarity, you end up with incompatible, spec-compliant implementations. The Go team officially maintains two implementations, gc and gccgo, to ensure that implementation doesn't end up ruling over the specification as has happened in other languages. There are also other third party implementations, including tinygo. Which spec-induced incompatibilities across these implementations are you referring to?
- oxnrtr 5y agoGo doesn't have a one-page spec, so what do you expect the GP to point to? You are proving his point.
- randomdata 5y agoLooks like one page to me: https://go.dev/ref/spec https://go.dev/ref/spec
- oxnrtr 5y agoYeah, no.
- randomdata 5y agoFeel free to show us the second page.
- josephcsible 5y agoIt starts about 2/3 of the way through the table of contents.
- randomdata 5y agoA link is fine.