Yeah it’s a bit inaccurate to say it’s not supported. It just has edge case handling written explicitly into whatever thing you’re building (I assume it’s required to do so in order to be well-typed). It took this idea from Haskell, which might have gotten it from Miranda or something.
I like the pattern a lot more. It makes you just initialize the value and only keep it ‘nullable’ for where it’s needed and then you need to check. Even .net implemented it (but a bit more awkward)
Rust is neat because it doesn’t have the bottom 2
Lack of support for nulls sounds like a huge pain in the ass.
It has std:option
So every object that can be None or Some, needs to be checked when used. And only options can be set to None
Yeah it’s a bit inaccurate to say it’s not supported. It just has edge case handling written explicitly into whatever thing you’re building (I assume it’s required to do so in order to be well-typed). It took this idea from Haskell, which might have gotten it from Miranda or something.
I like the pattern a lot more. It makes you just initialize the value and only keep it ‘nullable’ for where it’s needed and then you need to check. Even .net implemented it (but a bit more awkward)
Yup. Programmers are really stupid, if the compiler forces us to explicitly handle weird situations that’s a feature.
*Laughs in Option<T>*
It also doesn’t have throw/try/catch. If a function can fail, it returns a Result and you have to deal with the failure case explicitly.