My intelligence is that of a ping pong ball but think it's time to clean up de go compiler backlog so ping pong balls like me have a chance to understand the compiler code.
For example from the compiler readme ``` Note that the `go/*` family of packages, such as `go/parser` and `go/types`, have no relation to the compiler. Since the compiler was initially written in C, the `go/*` packages were developed to enable writing tools working with Go code, such as `gofmt` and `vet`. ``` Assuming it doesn't refer to /usr/local/go/src/go but to /usr/local/go/src/cmd/go can we remove this completely to prevent confusion and eliminate dead code especially in very complicated stuff like compiler code. I think clarity is nr 1 priority before any new feature? And then there is /usr/local/go/src/cmd/vendor which my first instinct was based on the folder structure. 'O that must be the place where they implement the vendor mechanism.` But then I realised its actually a vendor map which is even more confusing when go modules is suppose to be the thing for this now. Also before we steam role Go 2.0 can we for example address this first? ``` The gc package includes an AST definition carried over from when it was written in C. All of its code is written in terms of it, so the first thing that the gc package must do is convert the syntax package's syntax tree to the compiler's AST representation. This extra step may be refactored away in the future. ``` I am sure every single thing has a perfect reason and explanation, but I am just giving feedback that me the ping pong ball will never be able to understand how to change even the tiniest thing in there. For example I wanted to just try https://go-review.googlesource.com/c/go/+/184818 and from trying to find documentation and asking github issues / golang-nuts / golang slack to help me, only a select few are able to help me with it. Understandably they don't have time to explain it all. But this is for me a big warning that the Go compiler itself is still very heavily dependant on a few individuals who truly understand the compiler inside out. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/b6ff09e7-4e6f-433e-8130-d3b2e60e23ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
