Conversation
This matches a change made in ECMA-402 to canonicalize calendar identifiers. Anba already made the corresponding spec text change. Closes: #2908
Ms2ger
approved these changes
Jul 5, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Anba re-synced the spec text with the latest draft of ECMA-402 in #2904. That brought in AvailableCalendars which now needs to move into ECMA-262 as part of Temporal, and also brought in calendar canonicalization which I've implemented support for in the reference code. Also brings in a test262 update with improved coverage for calendar canonicalization.