Avoid the creation of meaningless ranges (nil, false, true)
With the definition of <=> on Object on post 1.8, the range_init() function no more throws "ArgumentError: bad value for range" when creating these ranges:
These kind of ranges are meaningless, the majority of methods on Range do not work on them, like (nil..nil).include?(nil).
This feature request (with patch) re-introduces the 1.8 behaviour of throwing ArgumentError when creating such ranges.
No data to display