3 ms·
The right solution would've been to go for algebraic data types or at least nullable types. The justification for not going down the former route was that they
by talideon 10y ago
The right solution would've been to go for algebraic data types or at least nullable types. The justification for not going down the former route was that they overlapped too much with interfaces, which is a justification I'm not exactly convinced by. Algebraic data types would make error handling in Go a heck of a lot more pleasant to boot.
- Ar-Curunir 10y agoYes, but that would involve looking at the last 30 years of PL Research, which the parent claims they chose nebulous "experience" over. I get that that the inventors of Go are respected people, but even they can mistakes.