On Tue, Dec 30, 2008 at 10:31:47AM +0900, Ryan Davis wrote:
> On Dec 29, 2008, at 17:13 , Yukihiro Matsumoto wrote:
>> It's intentional.  Ruby's flexibility sometimes allows you to do some
>> nasty things.  Ruby consider you smart enough to avoid such
>> contradiction.
>
> ok... but why?

In ruby-libjit I define == operator on JIT types to emit an eq
instruction.  Now that != is redefinable I can use it to emit an neq
instruction (instead of always returning false, which is what it does on
1.8).

Paul