Skip to content

Conversation

@Manishearth
Copy link
Contributor

endOfMonth.Day is a valid day value, we should not be erroring for it.

@Manishearth
Copy link
Contributor Author

r? @ptomato @sffc

aarongable pushed a commit to chromium/chromium that referenced this pull request Nov 24, 2025
Uplifts unicode-org/icu4x#7257

Caused by spec bug: tc39/proposal-intl-era-monthcode#98

Change-Id: I5df814a7ef7c2c8b1e44affd34fd31d017c04b28
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7201147
Auto-Submit: Manish Goregaokar <manishearth@google.com>
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1549444}
Copy link
Collaborator

@sffc sffc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recall thinking that this condition didn't matter for < vs <= because the resulting day is the same either way, but then I think the overflow reject got grafted in a bit later and made it matter whether < or <= is used. Thanks for the catch

Manishearth added a commit to unicode-org/icu4x that referenced this pull request Nov 25, 2025
Copy link
Collaborator

@ptomato ptomato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had been hoping to write a test to verify this similar to what Ben and I have been doing for #101. But I don't think I'll have time and I don't want to be the bottleneck here. LGTM with that caveat.

Note that there is identical language in NonISODateSurpasses, but there it really does not matter because the "If overflow is REJECT" step is not present. We could change to ≤ there just for consistency, or leave it as-is. I don't have a strong opinion.

@sffc
Copy link
Collaborator

sffc commented Dec 11, 2025

Note that there is identical language in NonISODateSurpasses, but there it really does not matter because the "If overflow is REJECT" step is not present. We could change to ≤ there just for consistency, or leave it as-is. I don't have a strong opinion.

Good catch. I favor consistency between those two AOs.

mohd-akram pushed a commit to gsource-mirror/chromium-src-third_party-rust that referenced this pull request Jan 9, 2026
Uplifts unicode-org/icu4x#7257

Caused by spec bug: tc39/proposal-intl-era-monthcode#98

Change-Id: I5df814a7ef7c2c8b1e44affd34fd31d017c04b28
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7201147
Auto-Submit: Manish Goregaokar <manishearth@google.com>
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1549444}
NOKEYCHECK=True
GitOrigin-RevId: 02da9f75c4cb912e2dd0e0fdad60803d207f06aa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants