sqlread VS go-retry

> Use int-type enums with iota: no human-readable error values, no compile-time guard against illegal enum values

Create a new int type and use that for your enums. You have to try really hard to get a bad value in that case, and if it’s an unpunished type in a different package it’s even harder.

See:

https://github.com/donatj/sqlread/blob/91b4f07370d12d697d18a...

I was also curious so I picked a likely-looking project on his github and indeed found an attempt to handle a channel "deterministically" at https://github.com/sethvargo/go-retry/blob/main/retry.go#L51

Honestly the whole first select seems redundant; any code that relies on this is broken. But OK, maybe you do have some strange performance case where this matters? In that case the whole thing could be more succinctly solved by looping on `for ctx.Err() == nil` instead of infinitely.

It also leaks the timer until it fires if the context cancels, which seems like it would be more of a practical performance problem than any overhead to the additional elect.