Re:Don't overload #nil? in Ruby
by sleight42 on Thursday November 10, 2011 @02:03PM
(#3221318)
That added flexibility comes at the cost of standardization.
There are practical reasons that we're not all coding in IO. Allowing for the redefinition of control primitives is a slippery slope. In short order, we may have apps that read well to us but aren't clear to others.
There are practical reasons that we're not all coding in IO. Allowing for the redefinition of control primitives is a slippery slope. In short order, we may have apps that read well to us but aren't clear to others.