Hacker News Reader

I'm looking forward to the improved editor experience as gopls is now workspace-aware.

There's a couple of repos at work which contain multiple Go modules (each in their own subdirectory, with their own go.mod files). It's a bit of a pain to get LSP working correctly for each individual module if I open the root directory of the repo in my editor.

View on HN

> There's a couple of repos at work which contain multiple Go modules (each in their own subdirectory, with their own go.mod files).

There's almost no reason to do this. 1 repo = 1 module. Even for monorepos.

Can you elaborate? What if you have multiple commands (main.go) with differing dependencies?

They can (and usually should) exist in a single module. Each compiled artifact will link in only the dependencies it requires, not all of the dependencies of the parent module.

Reply on news.ycombinator.com