Fix behavior Hash#eql? #1823

Merged
merged 1 commit into from Mar 7, 2014

Conversation

Projects
None yet
2 participants
@ksss
Contributor

ksss commented Mar 7, 2014

This behavior specification of mruby?

> 1.eql?(1.0)
 => false
> [1].eql?([1.0])
 => false
> {a:1}.eql?({a:1.0})
 => true

I think it's should be that.

> 1.eql?(1.0)
 => false
> [1].eql?([1.0])
 => false
> {a:1}.eql?({a:1.0})
 => false

matz added a commit that referenced this pull request Mar 7, 2014

@matz matz merged commit 23853ac into mruby:master Mar 7, 2014

1 check passed

default The Travis CI build passed
Details

ksss added a commit to ksss/mruby that referenced this pull request Mar 8, 2014

matz added a commit that referenced this pull request Mar 8, 2014

ghost pushed a commit to iij/mruby that referenced this pull request Mar 11, 2014

ghost pushed a commit to iij/mruby that referenced this pull request Mar 11, 2014

@ksss ksss deleted the ksss:hash-eql branch Mar 16, 2014

mattn added a commit to mattn/mruby that referenced this pull request Sep 11, 2015

mattn added a commit to mattn/mruby that referenced this pull request Sep 11, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment