Our great sponsors
-
The explanation you refer to later in the piece assumes we are using fat pointers, but the earlier part is referring to the use of fat pointers in the first place (or more broadly the lack of covariance). Taking a look at https://github.com/golang/go/issues/7512 it looks like the lack of covariance stays because of the complexity cost in the language to support it
-
Yes it is: https://github.com/uber-go/guide/issues/25
-
Mergify
Updating dependencies is time-consuming.. Solutions like Dependabot or Renovate update but don't merge dependencies. You need to do it manually while it could be fully automated! Add a Merge Queue to your workflow and stop caring about PR management & merging. Try Mergify for free.
-
Can I highjack a topic? Made a linter recently that will track usage of returned values, just to follow rule return concrete values instead interfaces- ireturn. Can be configurable, can be used with github-actions and will be available with next minor version of golangci-lint.
