Support July 2024 version of Temporal API

[rauschma]

• June 2024 – major changes (most of the changes were simplifications, if I understand correctly): https://github.com/tc39/notes/blob/f83fd756ecbac62fef3efab07dee7255bd98509b/meetings/2024-06/june-12.md#temporal-stage-3-update-and-scope-reduction
• July 2024 – minor changes: https://github.com/tc39/notes/blob/HEAD/meetings/2024-07/july-30.md#temporal-update--bug-fixes

(As an aside: The comparison table in the readme is very helpful, especially the dates/versions of the supported APIs. 🙏)

[arshaw]

Definitely. I hope to get this done this month.

[rauschma]

Excellent! I’m really looking forward to using the final Temporal API in my projects.

[arshaw]

Correction: it will be sometime this quarter. Apologies for the delay.

[o-t-w]

Is anybody working on this?
Is there a simple list of everything that needs to be removed?

I'd be happy to do a PR for
some of the changes.

[rauschma]

FWIW – these are two links I’ve had on my “read in the future” list for a while; maybe they are useful:

• Slides: https://docs.google.com/presentation/d/1PPMAxVnVjFwRPuJwOvVsw9nZLQ6jDM8Hd5PNO0Grp4I
• https://linkedlist.ch/temporal_scope_reduction_66/

[fabon-f]

Also we have to update the forked version of test262 under fullcalendar org (https://github.com/fullcalendar/test262 ), but there are several choices how to update it: merge upstream little by little, or bigbang pull request all at once? There are several changes only in forked version and perhaps merging isn't obvious.

I'm concerned that practically only core maintainers who know the context well can make this change (coming pull requests for forked test262 can be hard to review for maintainers in terms of both quality and quantity).

[arshaw]

Hello everyone, apologies for delay in in updating to the latest spec, I've been swamped with the latest major release of FullCalendar (which pays the bills). I am still very excited to implement the reduced-scope Temporal spec, especially because it will result in a smaller polyfill (potentially going from 20kb -> 17kb, but who knows).

I don't have a definitive list of things that changed since the last spec update (temporal-polyfill uses Apr 2024), but honestly it doesn't really matter because I plan to rip out the obvious things like Calendar and TimeZone classes, any logic that accepts/emits them, add ZonedDateTime::getTimeZoneTransition, then run test262 and let the failures guide me. The failures will jog my memory from past discussions in Temporal champions meetings.

As far as test262, the fullcalendar fork changed to correct diffing/rounding bugs in the spec, which are now fixed, and relaxed conformance for Calendar/TimeZone, which have now been removed. So, in theory, this polyfill should have perfect compliance with the unaltered test262 suite. That's where I plan to start: with the latest tc39/test262.

Unfortunately, I won't have bandwidth to resume this work until FullCalendar v7 launches, which is slated for Feb 14th. It might be possible for someone to aid in the meantime, but honestly running the test262 suite will be overwhelming for most.