2 ms·
what is also concerning, Go team years ago did small vote, small survey of positive occurrences, and decided to enforce it globally for anyone. old design give
by nikolayasdf123 2y ago
what is also concerning, Go team years ago did small vote, small survey of positive occurrences, and decided to enforce it globally for anyone.
old design give people option to use `tools.go` approach, or other, or nothing at all. now they are enforcing this `tools.go` standard. Go looks to be moving into very restrictive territories.
what about surveying opposing views? what about people who did not use `tools.go`
what is going on in Google, Go team?
- arccy 2y agoyou don't have to use this feature if you don't like it...
- nikolayasdf123 2y agoI was so concerned, because it seemed to me "you will not have any other choice". after digging deeper, it is alright
- nikolayasdf123 2y agoUPD: check this github comment. https://github.com/golang/go/issues/48429#issuecomment-2618445287 https://github.com/golang/go/issues/48429#issuecomment-26184... basically it go tool relies heavily on go module pruning, so transitive dependencies from tools are not propagated downstream. also, official docs say this: https://tip.golang.org/doc/modules/managing-dependencies#tools https://tip.golang.org/doc/modules/managing-dependencies#too... > Due to module pruning, when you depend on a module that itself has a tool dependency, requirements that exist just to satisfy that tool dependency do not usually become requirements of your module.