I think I could probably do that in my case, but that's so…

Samuel 8 Jan 2024

ok I'm sorry but I've decided Swift sucks. tried to implement an OpenAPI client for the TfL Unified API and it doesn't work because Swift doesn't allow milliseconds in their time stamps??

2 9

Bossett 8 Jan 2024

NSDate().timeIntervalSince1970 returns a TimeInterval which claims 'sub-millisecond precision over a range of 10,000 years' - so is this just ISO 8601 being annoying about fractional seconds?

TimeInterval | Apple Developer Documentation

From what I’ve seen, it’s actually Swift implementing a subset of the ISO spec by default when you use .withInternetDateTime I think you can enable it with the .withFractionalSeconds format option but now I need to go digging around in the OpenAPI client code

2 6

Samuel 8 Jan 2024

forums.swift.org/t/iso8601dat... oh boy - turns out enabling that option makes the milliseconds *mandatory*

ISO8601DateFormatter fails to parse a valid ISO-8601 date

When encoding iso8601 dates you might want careful control of the format. When decoding iso8601 dates I think you want a lenient parser, especially if you're writing a parser that will be the default ...

forums.swift.org

2 6

Samuel

@samuel.fm

I think I could probably do that in my case, but that's so stupid

1 5

Bossett 8 Jan 2024

Faithful implementation of ISO 8601 always strikes me as straight-up malicious compliance. Some Apple engineer screaming "Screw this! I'm going to make it work AS WRITTEN!".

1 26

David Buchanan 8 Jan 2024

ISO 8601 is a psyop

2 11