Dysfunctional Options Pattern in Go

Re:Dysfunctional Options Pattern in Go by ivanjermakov on Saturday July 20, 2024 @04:17PM (#41019444)

The problem with options in non-ML languages is that invalid state is unrepresentable[1]. E.g, in Java Option<Integer> can either be null, empty, some with null and some with a number.

To solve this problem, a language have to disallow null/nil as a bottom type and provide nice syntax to initialize types with optional types.

[1]: https://geeklaunch.io/blog/make-invalid-states-unrepresentab...

[ Parent | on HN ]

Re:Dysfunctional Options Pattern in Go by mmaniac on Thursday July 25, 2024 @09:58AM (#41068770)

Optional types don't fix this. The problem here is not having default (or named) function arguments. With optionals, you still have to pass every arg explicitly.

Languages with both of these features like Python don't end up using the builder pattern or reinventing it like this author.

[ Parent | on HN ]