4 ms·
At least two reasons I'm not choosing Go: - Go (the language) is missing the ability to declare something immutable. I don't mean making fields in a struct pri
by luuio 3y ago
At least two reasons I'm not choosing Go:
- Go (the language) is missing the ability to declare something immutable. I don't mean making fields in a struct private then exposing getters. I mean the equivalent of an immutable reference in Rust or `const ref` in C++.
- Go mod and go workspace still can't get a cohesive story together [1]:
- - If my module wants to depend on another module in a workspace, `go mod tidy` would freak out.
- - If I use replace in my go mod file to point to the other modules in the same workspace, `go mod vendor` will copy these workspace modules to the vendor folder as well.
[1] https://github.com/golang/go/issues/50750 https://github.com/golang/go/issues/50750