Issue #13933 has been updated by kyanagi (Kouhei Yanagita). While this is slightly off-topic, it's relevant to `MINIMUM`, so I'm noting it here. `0.0..Float::INFINITY` represents the entire range of floating-point numbers that is greater or equal to 0.0. Therefore, semantically, the range represented by `0.0..Float::INFINITY` should be the same as `0.0..`, but the following results contradict this: ``` (0.0..Float::INFINITY).cover?(0.0..) # => false (0.0..).cover?(0.0..Float::INFINITY) # => true ``` To make this work "correctly", we need the information that `Float::INFINITY` is the maximum value. If there is any handling regarding the minimum value, it might be necessary to have a similar approach for the maximum value as well. ---------------------------------------- Feature #13933: Add Range#empty? https://bugs.ruby-lang.org/issues/13933#change-104858 * Author: ted (Ted Johansson) * Status: Open * Priority: Normal ---------------------------------------- Range already responds to #size. It would be nice if it also responded to predicate #empty? :-) -- https://bugs.ruby-lang.org/