Bug #12961: Bad value for range using infinity for Date or Time

• Status: Closed
• Assignee: matz (Yukihiro Matsumoto)
• Target version: -
• ruby -v: ruby 2.3.2p217 (2016-11-15 revision 56796) [x86_64-darwin16]
• Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN

[loudandwicked (Damjan Cilenšek)]

How to reproduce:

-Float::INFINITY...Float::INFINITY # works
Date.today...Float::INFINITY # works
-Float::INFINITY...Date.today # fails with "ArgumentError: bad value for range"
Time.now...Float::INFINITY #fails with "ArgumentError: bad value for range"
-Float::INFINITY...Time.now #fails with "ArgumentError: bad value for range"

There's one similar bug report for 1.9.3, obviously still not resolved

[shyouhei (Shyouhei Urabe)]

• Status changed from Open to Assigned

Matz, please decide how it should work.

[znz (Kazuhiro NISHIYAMA)]

• Assignee set to matz (Yukihiro Matsumoto)

Ruby 2.6 supports endless range, and ruby 2.7 will support beginless range.

[matz (Yukihiro Matsumoto)]

Since both Time and Date work with float numbers at the other ends of the ranges, it should accept Float::INFINITY as well.

Matz.

[naruse (Yui NARUSE)]

matz (Yukihiro Matsumoto) wrote:

Since both Time and Date work with float numbers at the other ends of the ranges, it should accept Float::INFINITY as well.

Matz.

It looks only Date supports float number.

[matz (Yukihiro Matsumoto)]

So we only need to fix Date class. I don't think we should enhance Time ranges to support Integer/Float.

Matz.

[jeremyevans0 (Jeremy Evans)]

I've submitted a pull request to allow -Float::Infinity...Date.today: https://github.com/ruby/date/pull/13

[jeremyevans0 (Jeremy Evans)]

• Status changed from Assigned to Closed