Re:Overhead of Returning Optional Values in Java and Rust
by pkolaczk on Saturday October 16, 2021 @02:48PM
(#28890339)
With Kotlin based approach to nulls you can't represent Option<Option<T>> values.
[ Parent
| on HN ]
Re:Overhead of Returning Optional Values in Java and Rust
by brabel on Saturday October 16, 2021 @03:00PM
(#28890435)
And that's a good thing, no? I've never met a good use cases for double-wrapping values like this.
Re:Overhead of Returning Optional Values in Java and Rust
by Zababa on Saturday October 16, 2021 @03:38PM
(#28890764)
I'm not an expert on Kotlin but this reminds me of JS promises. The issue was that by not supporting Promise<Promise<T>>, promises were not monadic. It look like the same issue in Kotlin.
Re:Overhead of Returning Optional Values in Java and Rust
by nemetroid on Saturday October 16, 2021 @04:13PM
(#28891054)
I thought this was a good example: https://news.ycombinator.com/item?id=28746293