Context’s are my favorite part of Go right now. Setting up a context with a timeout at top of my tests and errgroup waits at the end has been very useful to catch any accidental go routine leaks.
For me the tool dependencies are the nicest new feature and the one I see myself using soon!
Especially when collaborating with other people on the same codebase, it has been problematic when we use external tools like swag to generate docs for an API.
There was no simple way to fix the tool’s version for everyone working on the codebase, and we would each get different outputs when using different versions of the tool. That should now be a problem from the past!
Those test improvements are really nice. I see myself using
{t,b}.Contextandb.Loopimmediately.Context’s are my favorite part of Go right now. Setting up a context with a timeout at top of my tests and errgroup waits at the end has been very useful to catch any accidental go routine leaks.
For me the tool dependencies are the nicest new feature and the one I see myself using soon!
Especially when collaborating with other people on the same codebase, it has been problematic when we use external tools like
swagto generate docs for an API.There was no simple way to fix the tool’s version for everyone working on the codebase, and we would each get different outputs when using different versions of the tool. That should now be a problem from the past!
We solved that with Nix, but doing it via Go itself also makes sense, sure.