Remix.run Logo
▲ rhdunn a day ago

1. Have declared nullability (e.g. `String? foo` / `val foo: String?`)

2. Use null coalescing (e.g. `foo?.bar?.baz`)

Languages such as Kotlin and C# support this style o programming.

The thing that I don't like about Optional types (in e.g. Scala or Java) is that they are too verbose. For example, instead of:

    return foo?.bar?.baz ?? 0
you have something like:

    return foo.flatMap(_.bar).flatMap(_.baz).getOrElse(0);
This is even harder to read if you have more complicated logic, requiring implicit lambdas and other machinery.
▲glandium a day ago | parent | next [-]

You can mostly write the former in rust: https://rust.godbolt.org/z/5M6nr3dzs

There are caveats, such the function using ? having to return an Option, which can be worked around by using a closure.

I think try blocks will make this slightly easier.

▲kaelwd 16 hours ago | parent [-]

`(try { foo?.bar?.baz? }).unwrap_or(0)` is maybe more understandable at a glance than the closure version but still more verbose than other languages.

▲hiimkeks 18 hours ago | parent | prev | next [-]

To me, foo?.bar?.baz ?? 0 looks really hard to reason about, if I imagine it sits in the context of some wider processing code.

Explicit options nudge you towards a data model that handles the None/null case early, so you don't have to write code that does the coalescing. If you parse-dont-validate early, you more often than not end up with a data model that is simpler and easier to process.

But then, this also depends on the sort of code you write. In the code I write, matching/"if-let"ing on Options to understand their value and then translating that into some enum that encodes the value on the abstraction level of the domain or algorithm has often been really really helpful.

▲Fluorescence 16 hours ago | parent [-]

It's nice.

I'm an old developer... I recognise the instinct to resent and avoid new unfamiliar syntax when I've got something that works for me. After some resistance, I give it a go, maybe working on someone else's code that uses it... and then it's suddenly "damn, the lang designers knew what they were doing".

This is one of those. What you might miss is that nested optionality is often the cleanest accurate representation and not error states e.g. a hierarchy of capabilities as a tree of options getting progressively more fine-grained yet you need to work with fine-grained capabilities at the leaves.

Nested optionality appears to be a bad data-structure to avoid when the code it requires is verbose and gruelling. Workarounds to reshape or design for less gruelling code are anti-patterns, adding complexity not to model the problem but to solve a language design weakness, which this solves.

▲tcfhgj a day ago | parent | prev [-]

Both variants are just different syntax for the same thing.

▲nine_k 21 hours ago | parent | next [-]

The second is twice as long as the fist. The difference matters.

▲ 21 hours ago | parent | prev [-]
[deleted]