Issue #15712 has been updated by jeremyevans0 (Jeremy Evans).

Status changed from Feedback to Closed

DateTime deprecation documentation was added to date: https://github.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.

----------------------------------------
Bug #15712: DateTime#=== should be defined and compare date and time instead of just the date
https://bugs.ruby-lang.org/issues/15712#change-87731

* Author: localhostdotdev (localhost .dev)
* Status: Closed
* Priority: Normal
* ruby -v: ruby 2.7.0dev (2019-03-18 trunk 67296) [x86_64-darwin17]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
DateTime#=== is inherited from Date#=== without overwriting the #=== method, this leads to DateTime#=== comparing only dates and ignore the time part.

```
DateTime.new(2001, 2, 3) === DateTime.new(2001, 2, 3, 12)
=> false
```

I think this is not the expected behavior but existing code might rely on this.

Date#===: https://ruby-doc.org/stdlib-2.1.9/libdoc/date/rdoc/Date.html#method-i-3D-3D-3D

Source: https://medium.com/@dvandersluis/an-rspec-time-issue-and-its-not-about-timezones-a89bbd167b86





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

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>