New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comparison ops for DateTimes in Rakudo #4380
Comments
From @masak<masak> hm, we have comparison ops for Date objects but not for |
From @labsterNot sure this is an oversight. S02 says that comparison ops coerce to Num, doc says that they coerce with Real. Either way, me (and TimToady) aren't so sure that we should be overloading comparison operators in the core language. The wrong part might be the Date comparsions. I guess we could have a Numeric form of a DateTime, like DateTime.now.Instant.tai, but that doesn't seem to have the same kind of type safety. We can implement infix:<cmp>, so infix:<before> and <after> would work, but despite being the perfect word, it's too general for type checking. On Sun Jul 05 05:12:10 2015, masak wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
From @labsterComparison ops added in dac0167a, but I still feel like this behavior runs counter to S03#1332. On Sat Aug 22 16:33:41 2015, labster wrote:
|
From @AlexDanielI'd say it's TESTNEEDED for now. Maybe the the stuff from S03 should be spec-ed in tests and then we can have a separate ticket asking for these changes. On 2015-09-06 20:11:24, labster wrote:
|
From @moritzTests added in Raku/roast@ff0472adfc |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125555 (status was 'resolved')
Searchable as RT125555$
The text was updated successfully, but these errors were encountered: