2 ms·
T? is just syntactic sugar for Optional/Maybe, no?
by adastra22 4y ago
T? is just syntactic sugar for Optional/Maybe, no?
- MrJohz 4y agoRoughly, yes. But that's the point: an Optional type along with static typing preventing misuse can prevent these sorts of errors entirely.
- shirogane86x 4y agoI don't think that's quite true. It's sort of the same in how it's used, but the main difference is that T? (or T | null) is a union, and Optional/Maybe/Option is a sum type. Out of all the implementations I've seen, T? can't be nested - you can't have T??, whereas it's quite possible to have a Option<Option<T>> (and it's sometimes useful).
- dtech 4y agoIt's semantically similar but not syntactic sugar, since it is not translated to Optional or wrapper types, so it also doesn't incur the overhead of Optional. I actually like the language support more, as it flows a lot better than the (flat)map chain you get in monadic style. Similar to async/await v.s. Future.