For Sum Types: Golang's multiple return parameters are overrated

In this Go Experience Report I am going to make a case for sum types over multiple return parameters. Analysis of multiple return parameters I wrote a little tool which does some analysis of Go source code. Thank you to the go/types library. The tool simply counts the number of times multiple return parameters are used. I ran this tool over the standard library and these are the results: [Read More]

Monads for Go Programmers

Why? Monads are all about function composition and hiding the tedious part of it. After 7 years of being a Go programmer, typing if err != nil can become quite tedious. Everytime I type if err != nil I thank the Gophers for a readable language with great tooling, but at the same time I curse them for making me feel like I’m Bart Simpson in detention. I suspect I am not the only one, but [Read More]