1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Generalize the explanation of the side effect of the rb_equal() optimization

Browse Source
This commit is contained in:
Benoit Daloze 2020-05-06 00:24:29 +02:00
parent 48d509cefc
commit e79e5e0b40
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
object.c
View File

@ -154,8 +154,10 @@ case_equal(VALUE obj1, VALUE obj2) {
* identity check using using C's == (same as BasicObject#equal?).
* If that check fails, it calls #== dynamically.
* This optimization actually affects semantics,
* as Float::NAN == Float::NAN is false,
* but rb_equal(Float::NAN, Float::NAN) is true!
* because when #== returns false for the same object obj,
* rb_equal(obj, obj) would still return true.
* This happens for Float::NAN, where Float::NAN == Float::NAN
* is false, but rb_equal(Float::NAN, Float::NAN) is true.
*/
VALUE
rb_equal(VALUE obj1, VALUE obj2)