diff options
author | Emily Dobervich <emily@dobervich.com> | 2014-04-08 16:24:35 -0700 |
---|---|---|
committer | Emily Dobervich <emily@dobervich.com> | 2014-04-08 16:24:35 -0700 |
commit | 5aeb3cd3ac88a6a16b6d573e4bbad846938fd5a7 (patch) | |
tree | 9c8679086dbf776529c0cd2098f7351e78ad54e9 /actionpack/test/fixtures/symlink_parent/symlinked_layout.erb | |
parent | 30a41e76f6e21b3dbaf502331066d922b24304bf (diff) | |
download | rails-5aeb3cd3ac88a6a16b6d573e4bbad846938fd5a7.tar.gz rails-5aeb3cd3ac88a6a16b6d573e4bbad846938fd5a7.tar.bz2 rails-5aeb3cd3ac88a6a16b6d573e4bbad846938fd5a7.zip |
Fixed problem where `1.day.eql?(1.day)` is false
This fixes:
1.second.eql?(1.second) #=> false
The new `eql?` requires that `other` is an `ActiveSupport::Duration`.
This requirement makes `ActiveSupport::Duration`'s behavior consistent
with other numeric types in Ruby.
1.eql?(1.0) #=> false
1.0.eql?(1) #=> false
1.second.eql?(1) #=> false (was true)
1.eql?(1.second) #=> false
{ 1 => "foo", 1.0 => "bar" }
#=> { 1 => "foo", 1.0 => "bar" }
{ 1 => "foo", 1.second => "bar" }
# now => { 1 => "foo", 1.second => "bar" }
# was => { 1 => "bar" }
And though the behavior here hasn't changed, for reference:
1 == 1.0 #=> true
1.0 == 1 #=> true
1 == 1.second #=> true
1.second == 1 #=> true
Diffstat (limited to 'actionpack/test/fixtures/symlink_parent/symlinked_layout.erb')
0 files changed, 0 insertions, 0 deletions