From @Skarsnik

I work with a webservice (Discord) that provide timestamp in the ISO 8601 format.
The issue is that DateTime can't create an object from a timestamp string because it does not follow the ISO totally.

skarsnik@​piko​:~/perl6-discord$ perl6 -e 'DateTime.new("2015-12-11T20​:41​:10.562000+00​:00")'
Invalid DateTime string '2015-12-11T20​:41​:10.562000+00​:00'; use an ISO 8601 timestamp (yyyy-mm-ddThh​:mm​:ssZ or yyyy-mm-ddThh​:mm​:ss+01​:00) instead
  in block <unit> at -e​:1

skarsnik@​piko​:~/perl6-discord$

According to https://en.wikipedia.org/wiki/ISO_8601#Times (the last paragraph) it allows extra precision on the lowest order time element. (the 10.56200 part for this example)

From @Skarsnik

Le Jeu 17 Déc 2015 07​:05​:50, scolinet@​gmail.com a écrit :

I work with a webservice (Discord) that provide timestamp in the ISO
8601 format.
The issue is that DateTime can't create an object from a timestamp
string because it does not follow the ISO totally.

skarsnik@​piko​:~/perl6-discord$ perl6 -e 'DateTime.new("2015-12-
11T20​:41​:10.562000+00​:00")'
Invalid DateTime string '2015-12-11T20​:41​:10.562000+00​:00'; use an ISO
8601 timestamp (yyyy-mm-ddThh​:mm​:ssZ or yyyy-mm-ddThh​:mm​:ss+01​:00)
instead
in block <unit> at -e​:1

skarsnik@​piko​:~/perl6-discord$

According to https://en.wikipedia.org/wiki/ISO_8601#Times (the last
paragraph) it allows extra precision on the lowest order time element.
(the 10.56200 part for this example)

I leave this RT open, even if there is a support for it, but It does not follow the ISO totaly and the display is not recommanded

From @labster

On Tue Dec 22 11​:13​:27 2015, scolinet@​gmail.com wrote​:

I leave this RT open, even if there is a support for it, but It does
not follow the ISO totaly and the display is not recommanded

Is there else something specific that we need to change? If not, tests were added to roast with e7baf233, and this ticket is can be closed.

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

From @zoffixznet

Appears to work fine now and there are tests for it​: Raku/roast@e7baf233

Closing.

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