From: "matz (Yukihiro Matsumoto)" <matz@...>
Date: 2012-11-16T07:31:47+09:00
Subject: [ruby-core:49395] [ruby-trunk - Feature #7359][Rejected] #eql? and #equal? naming


Issue #7359 has been updated by matz (Yukihiro Matsumoto).

Status changed from Open to Rejected

Making them little more intuitive does not worth breaking millions of existing programs.

Matz.

----------------------------------------
Feature #7359: #eql? and #equal? naming
https://bugs.ruby-lang.org/issues/7359#change-32942

Author: aef (Alexander E. Fischer)
Status: Rejected
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: Next Major


In my opinion the difference between @#eql?@ and @#equal?@ is really unintuitive. How about making their difference more obvious by giving one of them a more accurate name?

My proposal is to rename @#equal?@ to @#identic?@.

If you deprecate #equal? at the same time, maybe in the far future it can have a comeback as an alias for #eql? to make those people happy who dislike to use abbreviations just to reduce the character count by two and simultaneously making it harder to read in a classical sense.

If you like it, let me know. Then I will provide a patch.


-- 
http://bugs.ruby-lang.org/