> Who loses by allowing users to do what they want? Everyone else who looks at your code who would have preferred them. I dabble with both Go and Haskell, and

> Who loses by allowing users to do what they want? Everyone else who looks at your code who would have preferred them. I dabble with both Go and Haskell, and this seems like the best of both worlds: from Go they enforce a uniform standard across libraries, coworkers' code, etc, and from Haskell, they're adopting the philosophy that "types are documentation". I, too, would be a little annoyed at documenting lambdas, like this, but I think it's eminently reasonable to require it for all top-level function definitions. And it sounds like from another comment here, that that's the case. :)