News for hackers. Stuff that matters.
Re:Don't overload #nil? in Ruby by schukin on Thursday November 10, 2011 @01:55AM (#3219223)
You probably shouldn't use 'nil' to mean 'false', but since pretty much every compiler / interpreter out there will take the same branch when given a condition that's either nil or false, I'd say it's much safer to stick w/ what's existed for decades rather than accommodate some sort of tri-state boolean.
Re:Don't overload #nil? in Ruby by Confusion on Thursday November 10, 2011 @02:09AM (#3219254)
Well, the tri-state boolean was a worst-case, but consistent, example. I did mention you should hardly ever need that ;)