go101 VS go-retry

Go101: An in-depth guide that explores Go's internals, perfect for understanding the language at a deeper level.

Go101 is a jewel of a resource. It’s a spec written by an impartial observer not worried about trying to make golang look good but instead giving you the understanding to avoid all the edge cases

https://go101.org/

How about this: https://go101.org/ might help :)

Go 101 books, which cover every corner of the language itself (syntax, semantics, compiler and runtime implementation) and make more detailed explanations than the official docs in several points. (Author here)

Sometimes, reality and theory are not consistent: https://github.com/go101/go101/blob/master/pages/optimizations/code/4-string-and-byte-slice/concat-with-stack-byte-slice_test.go

How about go 101 ?

https://go101.org/ - read this.

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.