3 ms·

I'm really hoping that gopls gets to 1.0 soon. I feel like gopls is the elephant in the room that's taking a lot of air from some of the smaller tools, and I'm

• atombender 7y ago
  I've been following it since the first public release. It's still, unfortunately, very buggy. I restart gopls perhaps 20-30 times a day, working in VSCode. I have to restart it every time I switch git branches or do other major file changes that completely break its mind. I try to report every bug I find, but bug-reporting is even more of a productivity killer than the bugs. It's often difficult to reproduce exactly when they depend on an exact order of events. Sometimes it's just seems infuriatingly like incompetence. After struggling for hours with gopls suddenly going insane the other day (i.e. even a restart wouldn't fix things), I realized gopls doesn't understand build tags, and will just fail in random ways on code that has a "// +build" comment. The gopls team knows perfectly well tags are not supported, but instead of warning you when you open the file, which would be the sensible option, they just let gopls mismanage it. I really hope gopls reaches maturity soon, or I'll have to consider GoLand instead, which seems to have gotten this right.
• adonese 7y ago
  It has gotten more fixes in the last couple of releases. I now in situation where it works in vscode as it used to with gopath. But yeah that was very painful