-
Lovro Bikic authored
Reverts https://github.com/rails/rails/pull/11474. For Range#each, Ruby raises the same error as did the monkey patch for an ActiveSupport::TimeWithZone boundary, there is no behavior change. For Range#step, Ruby versions < 3.4 raise the same error as did the monkey patch. Since Ruby >= 3.4, Range#step uses the #+ method on the boundary to generate range elements, which ActiveSupport::TimeWithZone implements. PR for more context: https://github.com/ruby/ruby/pull/7444
Lovro Bikic authoredReverts https://github.com/rails/rails/pull/11474. For Range#each, Ruby raises the same error as did the monkey patch for an ActiveSupport::TimeWithZone boundary, there is no behavior change. For Range#step, Ruby versions < 3.4 raise the same error as did the monkey patch. Since Ruby >= 3.4, Range#step uses the #+ method on the boundary to generate range elements, which ActiveSupport::TimeWithZone implements. PR for more context: https://github.com/ruby/ruby/pull/7444
Loading