In response to the issue #12211 Numeric::Time doesn't handle equality (eql? and equal?) correctly
Firstly I think "==" and "eql?" should have consisent return value
Secondly the behaviour "==" is a bit weird.
think about:
1.second ==  1
1 == 1.second
This is against intuition.
So, I think following should all return true:

1.second == 1.second
1.second.eql? 1.second

1.second == 1
1.second.eql? 1

1 == 1.second
1.eql? 1.second

This patch made all this true

running the test suite, there is an extra warning now
/vagrant/rails/activesupport/lib/active_support/core_ext/numeric/time.rb:44: warning: method redefined; discarding old eql?
In response to the issue #12211 Numeric::Time doesn't handle equality (eql? and equal?) correctly
(removed alias to :equal?)

Firstly I think "==" and "eql?" should have consisent return value
Secondly the behaviour "==" is a bit weird.
think about:
1.second ==  1
1 == 1.second
This is against intuition.
So, I think following should all return true:

1.second == 1.second
1.second.eql? 1.second

1.second == 1
1.second.eql? 1

1 == 1.second
1.eql? 1.second

This patch made all this true

running the test suite, there is an extra warning now
/vagrant/rails/activesupport/lib/active_support/core_ext/numeric/time.rb:44: warning: method redefined; discarding old eql?