4 ms·
> Yes, it is different. Stop complaining, do it, and it just works. Here is the tutorial. Right. And all tis is described in accessible form where exactly? Al
by dmitriid 6y ago
> Yes, it is different. Stop complaining, do it, and it just works. Here is the tutorial.
Right. And all tis is described in accessible form where exactly?
Also, here's the very helpful error that go spits at you: https://news.ycombinator.com/item?id=24432511 https://news.ycombinator.com/item?id=24432511
- geodel 6y agoIts been covered in detail here: https://blog.golang.org/using-go-modules https://blog.golang.org/using-go-modules
- dmitriid 6y agoI will quote the article were commenting on: > For what it's worth, the official Go Blog tried to clear the situation up some, and posted a write-up about it. > blog.golang.org/v2-go-modules > Even as a seasoned developer, I found this write-up somewhat impenetrable. For how important and unusual of a requirement this is, the write-up is not accessible enough. Somewhere in the comments someone mentioned that "the actual info" on modules is here: https://github.com/golang/go/wiki/Modules https://github.com/golang/go/wiki/Modules which is slightly better but for some reason isn't in the official docs, and also basically brushes aside things like actually specifying v2+ modules in go.mod. And as the article shows with links to examples, people forget to specify v2+ modules (yes, even Google forgets this), or just don't do the whole v2+ thing.