After sticking to "true" and "false" being "1" and "nil" for the entire project I'm adding explicit true/false & I'm sad I'm no longer LISP
-
-
Agreed. The question is should the "or" be "false" or something like an explicit "null".
-
False, in my mind. Because what would be the type of "null"?
-
NullType. For two reasons (1) I don't want null to be falsy (2) I want it to be possible to have a variable of type "boolean option"
-
(I want there to be user-configurable conversion rules— nim does this and it works great— so if they WANT falsy-null, they can turn that on)
End of conversation
New conversation -
-
-
Seconded. Rust's Option/Result work very well, and feel like a better general building block rather than special-case magic for null.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.