Re:Don't overload #nil? in Ruby
by DanielRibeiro on Thursday November 10, 2011 @09:06AM
(#3220054)
As a gem creator, is is terrible.
As a application creator, is is only bad when/if you open source part of it. Otherwise, you can always run the gems' tests against the compillation of your env.
As a application creator, is is only bad when/if you open source part of it. Otherwise, you can always run the gems' tests against the compillation of your env.