[ruby-core:100012] [Ruby master Bug#17169] Bad value for range using infinity for Time

[ruby-core:100012] [Ruby master Bug#17169] Bad value for range using infinity for Time

[sarcasm008]

Issue #17169 has been reported by isarcasm (Igor Tsykalo).

----------------------------------------
Bug #17169: Bad value for range using infinity for Time
https://bugs.ruby-lang.org/issues/17169

* Author: isarcasm (Igor Tsykalo)
* Status: Open
* Priority: Normal
* ruby -v: ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
How to reproduce:

``` ruby
-Float::INFINITY...Float::INFINITY # works
Date.today...Float::INFINITY # works
-Float::INFINITY...Date.today # works
Time.now...Float::INFINITY #fails with "ArgumentError: bad value for range"
-Float::INFINITY...Time.now #fails with "ArgumentError: bad value for range"
```
I don't see why there should be a difference in this respect between Date and Time

This is issue is related to https://bugs.ruby-lang.org/issues/12961 which is Closed but actually only fixed the Date case.

P.S.: The Time.now...Float::INFINITY works with Rails' ActiveSupport via Time monkey-patching. However, monkey patching Float feels riskier.

 



-- 
https://bugs.ruby-lang.org/

[ruby-core:100013] [Ruby master Bug#17169] Bad value for range using infinity for Time

[merch-redmine]

Issue #17169 has been updated by jeremyevans0 (Jeremy Evans).

Status changed from Open to Rejected

@matz already rejected enhancing Time ranges in https://bugs.ruby-lang.org/issues/12961#note-5: `So we only need to fix Date class. I don't think we should enhance Time ranges to support Integer/Float.`  So the current behavior is not a bug.  If you would like, we could switch this issue to a feature request, but considering it has already been rejected recently, I think it is unlikely to be accepted.

----------------------------------------
Bug #17169: Bad value for range using infinity for Time
https://bugs.ruby-lang.org/issues/17169#change-87563

* Author: isarcasm (Igor Tsykalo)
* Status: Rejected
* Priority: Normal
* ruby -v: ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
How to reproduce:

``` ruby
-Float::INFINITY...Float::INFINITY # works
Date.today...Float::INFINITY # works
-Float::INFINITY...Date.today # works
Time.now...Float::INFINITY #fails with "ArgumentError: bad value for range"
-Float::INFINITY...Time.now #fails with "ArgumentError: bad value for range"
```
I don't see why there should be a difference in this respect between Date and Time

This is issue is related to https://bugs.ruby-lang.org/issues/12961 which is Closed but actually only fixed the Date case.

P.S.: The Time.now...Float::INFINITY works with Rails' ActiveSupport via Time monkey-patching. However, monkey patching Float feels riskier.

 



-- 
https://bugs.ruby-lang.org/

[ruby-core:100228] [Ruby master Bug#17169] Bad value for range using infinity for Time

[nobu]

Issue #17169 has been updated by nobu (Nobuyoshi Nakada).


Probably, since ruby 2.7, you can use begin-less/end-less ranges instead.



----------------------------------------
Bug #17169: Bad value for range using infinity for Time
https://bugs.ruby-lang.org/issues/17169#change-87817

* Author: isarcasm (Igor Tsykalo)
* Status: Rejected
* Priority: Normal
* ruby -v: ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
How to reproduce:

``` ruby
-Float::INFINITY...Float::INFINITY # works
Date.today...Float::INFINITY # works
-Float::INFINITY...Date.today # works
Time.now...Float::INFINITY #fails with "ArgumentError: bad value for range"
-Float::INFINITY...Time.now #fails with "ArgumentError: bad value for range"
```
I don't see why there should be a difference in this respect between Date and Time

This is issue is related to https://bugs.ruby-lang.org/issues/12961 which is Closed but actually only fixed the Date case.

P.S.: The Time.now...Float::INFINITY works with Rails' ActiveSupport via Time monkey-patching. However, monkey patching Float feels riskier.

 



-- 
https://bugs.ruby-lang.org/