delta/ruby.git/test/ruby/test_range.rb, branch ruby_3_2 github.com: ruby/ruby.git Raise TypeError for endless non-numeric range include? 2022-11-24T23:18:44+00:00 Jeremy Evans code@jeremyevans.net 2022-08-19T20:19:03+00:00 04a92a6764bf678919cf4b68a27496a39d6b886a Beginless ranges previously raised TypeError for this case, except for string ranges, which had unexpected behavior: ('a'..'z').include?('ww') # false (..'z').include?('ww') # previously true, now TypeError Use of include? with endless ranges could previously result in an infinite loop. This splits off a range_string_cover_internal function from range_include_internal. Fixes [Bug #18580] 
Beginless ranges previously raised TypeError for this case,
except for string ranges, which had unexpected behavior:

  ('a'..'z').include?('ww') # false
  (..'z').include?('ww') # previously true, now TypeError

Use of include? with endless ranges could previously result
in an infinite loop.

This splits off a range_string_cover_internal function from
range_include_internal.

Fixes [Bug #18580]
Range#size returns nil for (.."a") and (nil..) 2022-10-21T07:35:46+00:00 Yusuke Endoh mame@ruby-lang.org 2022-10-21T04:39:15+00:00 e026368061c56bc925aff58910a4b02f18b78c70 Fixes [Bug #18983] 
Fixes [Bug #18983]
Fix Range#cover? returning true for beginless ranges of different types 2022-06-06T16:59:22+00:00 Jeremy Evans code@jeremyevans.net 2022-04-22T02:46:17+00:00 c5475f42694eff35465c3332e0182c0611ca5918 Previously `(2..).cover?("2"..)` was false, but `(..2).cover?(.."2")` was true. This changes it so both are false, treating beginless ranges the same as endless ranges in regards to type checks. This also adds documentation to #cover? to describe behavior with beginless and endless ranges, testing each documentation example, which is how this bug was found. Fixes [Bug #18155] 
Previously `(2..).cover?("2"..)` was false, but
`(..2).cover?(.."2")` was true.  This changes it so both are false,
treating beginless ranges the same as endless ranges in regards to
type checks.

This also adds documentation to #cover? to describe behavior with
beginless and endless ranges, testing each documentation example,
which is how this bug was found.

Fixes [Bug #18155]
Fix Range#include? for beginless exclusive string ranges 2022-02-10T03:47:28+00:00 Jeremy Evans code@jeremyevans.net 2022-02-09T17:58:05+00:00 fd710d7e9995679db80b7adf35bbda2cd4db90c6 Previously, include? would return true for the end of the range, when it should return false because the range is exclusive. Research and Analysis by Victor Shepelev. Fixes [Bug #18577] 
Previously, include? would return true for the end of the range,
when it should return false because the range is exclusive.

Research and Analysis by Victor Shepelev.

Fixes [Bug #18577]
numeric.c, range.c: prohibit zero step 2020-10-23T06:26:51+00:00 Kenta Murata mrkn@users.noreply.github.com 2020-10-23T06:26:51+00:00 f754b422855131111092c0c147d744775cc4793f * numeric.c: prohibit zero step in Numeric#step * range.c: prohibit zero step in Range#step * Fix ruby-spec [Feature #15573] 
* numeric.c: prohibit zero step in Numeric#step

* range.c: prohibit zero step in Range#step

* Fix ruby-spec

[Feature #15573]
 freeze all Range objects. 2020-09-25T13:16:55+00:00 Koichi Sasada ko1@atdot.net 2020-09-25T09:05:55+00:00 0096d2b895395df5ab8696d3b6d444dc1b7730b6 Matz want to try to freeze all Range objects. [Feature #15504] 
Matz want to try to freeze all Range objects.
[Feature #15504]
Reapply "Special case Range#max for integer beginning and Float::Infinity end" (tests) 2020-09-02T01:02:12+00:00 Marc-Andre Lafortune github@marc-andre.ca 2020-09-02T00:26:45+00:00 94b54b038c1f4d6d2b54e10dd0305b1bc283449b Reverted in e080a4cdee 
Reverted in e080a4cdee
Revert "Fix Range#{max,minmax} for range with integer beginning and non-integer end" 2020-09-01T17:52:47+00:00 Jeremy Evans code@jeremyevans.net 2020-09-01T16:19:03+00:00 4db4faef0f96bfd3504f5eac454a0308c618ccd6 This reverts commit 8900a25581822759daca528d46a75e0b743fc22e. 
This reverts commit 8900a25581822759daca528d46a75e0b743fc22e.
Revert "Special case Range#max for integer beginning and Float::Infinity end" 2020-09-01T17:52:47+00:00 Jeremy Evans code@jeremyevans.net 2020-09-01T16:18:44+00:00 e080a4cdeeb55dddb6247ffd2563d2dc8b84c919 This reverts commit 05bf811c2839628aaef3d565daedb28be80d47ef. 
This reverts commit 05bf811c2839628aaef3d565daedb28be80d47ef.
Special case Range#max for integer beginning and Float::Infinity end 2020-07-19T14:25:55+00:00 Jeremy Evans code@jeremyevans.net 2020-07-16T17:11:35+00:00 05bf811c2839628aaef3d565daedb28be80d47ef Popular Ruby libraries such as Rails and Rubocop relying on the previous behavior, even though it is technically a bug. The correct behavior is probably raising RangeError, since that is what an endless range raises. Related to [Bug #17017] 
Popular Ruby libraries such as Rails and Rubocop relying on the
previous behavior, even though it is technically a bug. The
correct behavior is probably raising RangeError, since that is what
an endless range raises.

Related to [Bug #17017]