Go Modules have a v2+ problem ↦
Go has a problem. Go modules place a strange naming requirement on modules version 2 or greater. Module names on modules v2+ must end in the major version ala
…/v2, and communication of this rule has been weak. It’s non-obvious, and the community at large does not understand it.
I have seen many very large projects including Google owned projects get it wrong.
I brought the issue up at my local Go meetup, and no one had ever heard about the rule. They were very skeptical the rule existed at all.
Jesse goes on to tell the history, explain the problem in-depth, and suggest next steps for the Go Community.
Sign in or Join to comment or subscribe