I guess that overriding the behavior of any built-in classes in Ruby is not a gr... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

jasiek on Nov 10, 2011 | parent | context | favorite | on: Don't overload #nil? in Ruby

I guess that overriding the behavior of any built-in classes in Ruby is not a great idea, as most gems rely on that unmodified behavior.

DanielRibeiro on Nov 10, 2011 | [–]

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.

jaylevitt on Nov 10, 2011 | [–]

There's talk of "traits" for Ruby 2.0 that will let you scope your monkeypatching.

Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact