Thoroughly confusing lol. I think I need to check the spec in order to grasp this. I feel like this has more to do with the typing system rather than nil itself, maybe. I’ll see.
But yeah, this is nothing like null or undefined in JS, but more similar to NaN.
Yeah… It’s weird but I find it useful that it is, in a weird way. Treating it as an uncertainty means that one MUST explicitly check all pointers for nil as part of normal practice. This avoids NPEs.
Thoroughly confusing lol. I think I need to check the spec in order to grasp this. I feel like this has more to do with the typing system rather than
nilitself, maybe. I’ll see.But yeah, this is nothing like
nullorundefinedin JS, but more similar toNaN.Thank you for trying to explain!
Yeah… It’s weird but I find it useful that it is, in a weird way. Treating it as an uncertainty means that one MUST explicitly check all pointers for
nilas part of normal practice. This avoids NPEs.