From @masak

<masak> hm, we have comparison ops for Date objects but not for
DateTime objects... this is probably an oversight.
<masak> m​: my $dt1 = DateTime.now; my $dt2 = $dt1.later(​:1hour); say $dt1 < $dt2
<camelia> rakudo-moar 5919a8​: OUTPUT«Cannot call Real(DateTime​: ); [...]
* masak submits NYI rakudobug

From @labster

Not 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​:

<masak> hm, we have comparison ops for Date objects but not for
DateTime objects... this is probably an oversight.
<masak> m​: my $dt1 = DateTime.now; my $dt2 = $dt1.later(​:1hour); say
$dt1 < $dt2
<camelia> rakudo-moar 5919a8​: OUTPUT«Cannot call Real(DateTime​: );
[...]
* masak submits NYI rakudobug

The RT System itself - Status changed from 'new' to 'open'

From @labster

Comparison 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​:

Not 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​:

<masak> hm, we have comparison ops for Date objects but not for
DateTime objects... this is probably an oversight.
<masak> m​: my $dt1 = DateTime.now; my $dt2 = $dt1.later(​:1hour); say
$dt1 < $dt2
<camelia> rakudo-moar 5919a8​: OUTPUT«Cannot call Real(DateTime​: );
[...]
* masak submits NYI rakudobug

From @AlexDaniel

I'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​:

Comparison 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​:

Not 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​:

<masak> hm, we have comparison ops for Date objects but not for
DateTime objects... this is probably an oversight.
<masak> m​: my $dt1 = DateTime.now; my $dt2 = $dt1.later(​:1hour);
say
$dt1 < $dt2
<camelia> rakudo-moar 5919a8​: OUTPUT«Cannot call Real(DateTime​: );
[...]
* masak submits NYI rakudobug

From @moritz

Tests added in Raku/roast@ff0472adfc

@moritz - Status changed from 'open' to 'resolved'