tools

From the golang github org in non-toy code: 1. https://github.com/golang/tools/blob/f7d99c1a286d6ec8bd4516a... 2. https://github.com/golang/sync/blob/7fad2c9213e0821bd78435a9... There are dozens and dozens throughout the stdlib and other popular go code. The singleflight case is quite common, if you have: mu.Lock() if something() { mu.Unlock() moreWorkThatDoesntWantMutex() return } mu.Unlock() most gophers use manual lock/unlocks to be able to unlock early in an 'if' before a 'return', and that comes up often enough that it really does happen. I see manual lock/unlock all the time, and semi-regularly run into deadlocks caused by it. Maybe you don't use any third-party open source libraries, in which case, good for you congrats.

goimports has special-cased math/rand.Read vs crypto/rand.Read from basically the beginning. But https://github.com/golang/tools/commit/0835c735343e0d8e375f0... in 2016 references a time window where it could resolve "rand.Read" as "math/rand". Maybe you were in that time window?

The language has a tool that does this, and every editor I can think of uses it (https://github.com/golang/tools/tree/master/cmd/guru), specifically implements.go if you're interested.

Every major editor I can think of has a way to find out what implements an interface using guru (https://github.com/golang/tools/tree/master/cmd/guru). In VSCode, it's right-click -> Find All Implementations. vim-go has :GoImplements. Using go-mode, emacs provides go-guru-implements.

> I resent having to write three lines of boilerplate every time I want to reverse a slice. Up above I talk about gopls's postfix completions, and reversing a slice is one: https://github.com/golang/tools/releases/tag/gopls%2Fv0.7.0

gopls seems to be integrating some of the "tricks" into editor completion. This one isn't there, but other idioms are. (With gopls > 0.7.0, it's enabled by default. Details: https://github.com/golang/tools/releases/tag/gopls%2Fv0.7.0)

VSCode still works fine with Go, but I do agree that Goland is better. Gopls[0] (the Go language server) has definitely been getting better, but it was not-so-great for a while (it locks up from time-to-time and you have to restart it, but that may be better now). [0] https://github.com/golang/tools/blob/master/gopls/README.md

`go install golang.org/x/tools/present` finished on the author's contact information. At first I thought it was weird, and after experience, it's a great slide to end on. Now that I've watched Prof Winston's talk, I realise it's inspired. Thought it does say "Thank you" on the last slide. Oops. https://github.com/golang/tools/blob/master/cmd/present/temp...

The website is maintained by SourceGraph so of course there’s going to be some bias. That being said, the website is editable on GitHub [1] so people can submit fixes if needed. I’ve been using “gopls” [2] since Feb 2019 and I’m very happy with the functionality. Rebecca Stambler, Heschi Kreinick, Muir Manders and the rest of the team are doing a wonderful job. I encourage everyone to join the #gopls channel in the Gophers Slack group [3] to follow the updates. [1] https://github.com/langserver/langserver.github.io [2] https://github.com/golang/tools/tree/master/gopls [3] https://invite.slack.golangbridge.org/

it made it painful for a while, but GoLand and VSCode both support modules at this point (though VSCode uses the gopls[1] (language server), that I've been having mixed results with). [1] https://github.com/golang/tools/tree/master/gopls

I see now about a month ago it was renamed gopls, at least for the user facing command. https://github.com/golang/tools/tree/master/cmd/gopls There's also a vscode directory, so maybe it's worth checking out. I'm guessing it's too soon, but at least I know where to look more closely now.

There is a language server merged into the "tools" repo [1], so something is definitely in the works! 1: https://github.com/golang/tools/tree/master/internal/lsp