From: "tadf (tadayoshi funaba)" <redmine@...>
Date: 2013-05-27T19:55:20+09:00
Subject: [ruby-core:55178] [ruby-trunk - Bug #8454][Rejected] Date and Time compatibility


Issue #8454 has been updated by tadf (tadayoshi funaba).

Status changed from Open to Rejected

it's the current spec.
see [ruby-dev:24250].

i think you are interested in the following case too.

> Time.parse('2001-02-03')
#=> 2001-02-03 00:00:00 +0900

> Date.parse('2001-02-03')
#=> #<Date: 2001-02-03 ((2451944j,0s,0n),+0s,2299161j)>

> DateTime.parse('2001-02-03')
#=> #<DateTime: 2001-02-03T00:00:00+00:00 ((2451944j,0s,0n),+0s,2299161j)>

i honestly don't like this feature.
but i think i just provided what users want in this case.

----------------------------------------
Bug #8454: Date and Time compatibility
https://bugs.ruby-lang.org/issues/8454#change-39543

Author: jonys (Jonatan Hejzlar)
Status: Rejected
Priority: Normal
Assignee: 
Category: ext
Target version: 
ruby -v: 2.0.0p195
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


Time.to_datetime creates a DateTime object with the local timezone
Date.to_datetime creates a DateTime object with the +0000 timezone

As a result, Date.to_time.to_datetime gives a different result than Date.to_datetime.


-- 
http://bugs.ruby-lang.org/