3 ms·
for everyone else that was confused about why an article titled > Go 1.17 is deprecating the traditional use of 'go get' did not link to the original proposal
by jd3 5y ago
for everyone else that was confused about why an article titled
> Go 1.17 is deprecating the traditional use of 'go get'
did not link to the original proposal/implementation issues:
initial proposal: https://github.com/golang/go/issues/40276 https://github.com/golang/go/issues/40276
1.16 deprecation delay: https://github.com/golang/go/issues/42885 https://github.com/golang/go/issues/42885
1.17 deprecation: https://github.com/golang/go/issues/43684 https://github.com/golang/go/issues/43684