[masklinn]

> yes, it is clearer the Go way.

Hardly, but that's not the argument, I was replying to an assertion that not having default arguments enforces you to actually design an elegant API. It does no such thing. Contrary to the person I was replying to (and to you apparently) I would say that there are advantages to and issues with both options, but the claim I quoted and replied to is just plain insane.

> things are up-front and obvious, easier to document, and less error-prone.

Things are none of these, the exact same claim can be made about having optional parameters and against not having them.