Project

General

Profile

Actions

Bug #21147

open

[Breaking changes or Bug] DateTime Range#to_a behaves different between 3.3.7 and 3.4.1

Added by jamesst20 (James St-Pierre) 4 days ago. Updated 4 days ago.

Status:
Open
Assignee:
-
Target version:
-
ruby -v:
ruby 3.3.7 (2025-01-15 revision be31f993d7) [arm64-darwin24], ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +PRISM [arm64-darwin24]
[ruby-core:121101]

Description

a = Time.zone.now.to_date
b = Time.zone.now.to_date

# Ruby 3.3.7
(a..b).to_a
=> [Tue, 18 Feb 2025] 

# Ruby 3.4.1
(a..b).to_a
=> [] 

Related issues 1 (0 open1 closed)

Related to Ruby master - Bug #21030: Bug: #step with Range<ActiveSupport::Duration> behavior broken on Ruby 3.4.1Closedzverok (Victor Shepelev)Actions

Updated by jamesst20 (James St-Pierre) 4 days ago

Sorry, the exemple above is incorrect.

Pure Ruby reproductible

require 'date'
require 'json'

a = Time.now.to_date

# Ruby 3.3.7
(a..a).step(7).to_a
# => [Tue, 18 Feb 2025]

# Ruby 3.4.1
(a..a).step(7).to_a
# => []
Actions #2

Updated by mame (Yusuke Endoh) 4 days ago

  • Related to Bug #21030: Bug: #step with Range<ActiveSupport::Duration> behavior broken on Ruby 3.4.1 added
Actions

Also available in: Atom PDF

Like0
Like0Like0