You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common problem I have with the different flavors of pools is that I forget to wait for the result. This problem is conceptually similar to how zerolog requires you to remember to call Msg{f} on the log event for it to be effectuated.
In the case of zerolog, this is solved by zerologlint. This is further bundled by golangci-lint, which makes it really easy to verify I remember to call the appropriate methods.
It would be fantastic if we had something similar for this module!
The text was updated successfully, but these errors were encountered:
A common problem I have with the different flavors of pools is that I forget to wait for the result. This problem is conceptually similar to how zerolog requires you to remember to call
Msg{f}
on the log event for it to be effectuated.In the case of zerolog, this is solved by zerologlint. This is further bundled by golangci-lint, which makes it really easy to verify I remember to call the appropriate methods.
It would be fantastic if we had something similar for this module!
The text was updated successfully, but these errors were encountered: