News for hackers. Stuff that matters.
Re:One Program Written in Python, Go, and Rust by bkq on Tuesday July 02, 2019 @09:29AM (#20334739)
>What I like to do is to make the last arg take a struct such that you indirectly have named (and optional) arguments:

Rob Pike, and Dave Cheney both posted about this [1][2]. They summarised that using self-referential functions were a more optimal way for handling options to a function. This gives the benefit of allowing the options to be easily extensible by yourself, and any users that would be interacting with your API.

[1] - https://commandcenter.blogspot.com/2014/01/self-referential-...

[2] - https://dave.cheney.net/2014/10/17/functional-options-for-fr...

Re:One Program Written in Python, Go, and Rust by nemo1618 on Tuesday July 02, 2019 @10:28AM (#20335493)
Functional options were exciting when they were first discovered, and they're used in a few popular APIs (e.g. gRPC), but they haven't become as ubiquitous as you'd expect if they were truly superior. My guess is that a struct is the more direct and obvious approach for most people. Functional options also make it awkward to save and reuse a set of options later.