David Lobe

In my case it appears that `unparam` doesn't like the combination of a `map of functions` + `casting`. Examples: ```go func blah() { _ = map[int]func() ([]byte, error){ 0: func()...

Related issues: https://github.com/golangci/golangci-lint/issues/314 https://github.com/golangci/golangci-lint/issues/355

The easy path is to follow [semver rules](https://semver.org/) (see point 2) MAJOR version when you make incompatible API changes. And go for a new major version v2.0.0. That doesn't mean...

Hello @jirfag any news on this? What would be the plan on this? just updating staticcheck to latest version? In that case I think we should add a note that...

An idea to do not break backwards compatibility and do not deprecate older tools might be adding a property to staticcheck config, called, for example: `gte_2019_1: true` This flag (false...

Now that you are back @jirfag, I am still interested on moving this forward, and could take this. Just need some feedback on the proposed design.

@flimzy would you be open to recover this? It seems that `Connector` is the new way to go and that the drivers should start using that pattern instead. https://pkg.go.dev/database/sql/driver

> Any objection to me updating this PR to get it merged? That was fast! Truly appreciated.

Should we take the opportunity to implement the `DriverContext` interface as well? But maybe that's a separate PR.

Hey! This is the new way to write sql drivers, and I need I would need this to wrap txdb inside my own wrapper (adding retrial functionality, for example). See:...