You could have a very simple `match` with no nested patterns or guards, like Haskell's core language.

> Non-nullability requires generics for a result type which is a huge source of complexity.

Option could be another built-in generic like Map in Go. Or one could simply have to write a new Option type ever time. Sucks, but aren't go programmers used to this sort of thing?

> Generics impacts runtime efficiency.

False