go101 VS go-sumtype

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 find this implementation to be quite minimal and less clumsy than alternatives. Sure, you don't get nice exhaustive pattern matching. Also, type inference gets in the way when instantiating UserKey (though you can wrap it in constructor functions). But expressing your intent using types still makes your code much more convenient and easier to understand.

The call out to sum types is something I feel. I've been using Rust daily for almost 10 years now, and sum types are absolutely still one of the things I love most about it. It's easily one of the things I miss the most in other languages. I'm usually a proponent of "using languages as they're intended," but I missed exhaustiveness checking so much that I ported a version of it to Go[1] as a sort of lint.

[1]: https://github.com/BurntSushi/go-sumtype

A Google search for golang sum types currently shows my project as a second hit: https://github.com/BurntSushi/go-sumtype

I've been writing Go and Rust nearly daily for about a decade now (Go is more than a decade, Rust is about 8 years). You are not going to teach me anything about the pros and cons of either language in a reddit comment. I do not need to be taught about the "iota mess" when I've written tooling for exhaustiveness checking in Go.

https://github.com/BurntSushi/go-sumtype forces exhaustive type switches for interfaces specifically annotated to need that.

We can fix these two problems by relying on static analyzers such as go-sumtypes

See also https://github.com/BurntSushi/go-sumtype

go-sumtype[0] has completeness checking for sealed interfaces.

[0] https://github.com/BurntSushi/go-sumtype

Pretty easy to achieve outside of the compiler: https://github.com/BurntSushi/go-sumtype