> I'm sorry, but that API is not something to be proud of.
I agree: not only does using it require a lot of boilerplate, but Option takes several arguments and returns a value that only restores the previous value of the last option! That sounds very error prone, I'm sure someone will think the value return by Option undoes all of the option setting.
I don't know that sarcastic is the correct word, but I certainly wasn't completely serious. Maybe "playfully antagonistic".
I suppose the problem I have here is, if I was designing a language, and composability was a stated goal, then I wouldn't have come up with Go.
> a brilliant article from Rob Pike about using and composing functions to create flexible APIs
I'm sorry, but that API is not something to be proud of.