Bug #15712
closed
Updated by hsbt (Hiroshi SHIBATA) over 6 years ago
@localhostdotdev
I fixed an issue of our tracker. I deleted 15713-15716.
Updated by nobu (Nobuyoshi Nakada) over 6 years ago
- Status changed from Open to Feedback
What version of DateTime do you use?
With the trunk I got:
require 'date'
dt1 = DateTime.new(2001, 2, 3)
dt2 = DateTime.new(2001, 2, 3, 12)
p dt1 === dt2 #=> true
p dt1 == dt2 #=> false
Updated by localhostdotdev (localhost .dev) about 6 years ago
@nobu (Nobuyoshi Nakada) Not sure why I wrote false (maybe I confused === with == in my testing), I'm getting true on ruby 2.5.3, 2.6.1, 2.6.2 and ruby-head (2.7.0 (same as the one registered in the issue)).
rvm ruby-head do ruby -e 'require "date"; dt1 = DateTime.new(2001, 2, 3); dt2 = DateTime.new(2001, 2, 3, 12); puts "=== #{dt1 === dt2}"; puts "== #{dt1 == dt2 }"; puts RUBY_VERSION'
Updated by matz (Yukihiro Matsumoto) over 4 years ago
I admit it is a bug. But we consider use of DateTime should be discouraged. So we keep this bug behavior for compatibility's sake.
We are going to describe obsoletion in the document.
Matz.
Updated by jeremyevans0 (Jeremy Evans) over 4 years ago
- Status changed from Feedback to Closed
DateTime deprecation documentation was added to date: https://.com/ruby/date/commit/58ca6e6a3ee20c72a77266e0f74920b12a06ee9d
Date#=== is describes the current behavior as only considering the date, and uses examples with DateTime, so I think the situation is fully documented and I'm closing this.