go101 VS sqlread

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.

> 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...