Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go: [modules + integration] go mod requires, list the direct requirements for using a module #31308
This report is part of a series, filled at the request of @mdempsky, focused at making Go modules integrator-friendly.
Please do not close or mark it as duplicate before making sure you’ve read and understood the general context. A lot of work went into identifying problems points precisely.
Go needs an official
It is the pendant of
changed the title
[modules + integration] go mod requires, direct module use requirements
Apr 6, 2019
Short-term the only remaining showstopper for is issue #31304. I know how to workaround or get by without the others, in degraded mode¹.
Mid to long-term local workarounds and degraded mode are a terrible strategy. Once the language is no longer new and shiny (which will eventually happen to Go), people will actively resist getting involved in something that makes their integration work an obstacle course, and people already involved will migrate to bluer skyes. It’s not a single issue problem, it’s a death by a thousand papercuts problem, where each small tooling misbehaviour and missing functionnality contributes to human rejection.
¹ Workaround means reimplementing the Go tooling: