Editorial: Make explicit that ToTemporalYearMonth rejects too-large ISO year strings #3083
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.
The call to CalendarYearMonthFromFields will already reject too large dates, but adding an explicit step makes it more obvious that ISODateToFields doesn't require support for mapping large ISO dates to calendar dates. And it also aligns ToTemporalYearMonth with ToTemporalMonthDay after #3054.
Taken from @anba's PR #3054, this is the editorial/unobservable part.