Skip to content

ICU-23087 Pass null to applyPropertyAlias for a unary property query #3456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 28, 2025

Conversation

eggrobin
Copy link
Member

@eggrobin eggrobin commented Mar 26, 2025

This only affects users of the internal perpetually-@draft XSymbolTable (in particular, unicode-org/unicodetools). It makes it possible to distinguish \p{X} (the characters that have binary property X, or that have gc X or script X) from \p{X=} (the characters for which property X is the empty string).

Note that ICU allows \p{Whitespace=} for \p{Whitespace}, or \p{L=} for \p{L}. This remains the case with this change, so the public API is unaffected.

Checklist

  • Required: Issue filed: ICU-23087
  • Required: The PR title must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
  • Required: Each commit message must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
  • Issue accepted (done by Technical Committee after discussion)
  • Tests included, if applicable
  • API docs and/or User Guide docs changed or added, if applicable

macchiati
macchiati previously approved these changes Mar 26, 2025
Copy link
Member

@macchiati macchiati left a comment

Choose a reason for hiding this comment

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

Great idea!

@markusicu markusicu self-assigned this Mar 27, 2025
@markusicu
Copy link
Member

Note that ICU allows \p{Whitespace=} for \p{Whitespace}, or \p{L=} for \p{L}. This remains the case with this change, so the public API is unaffected.

I think we can & should propose to change those to errors.

@eggrobin
Copy link
Member Author

I think we can & should propose to change those to errors.

I agree. But there will be more changes to UnicodeSet behaviour coming as part of the standardization, so I would like to do that when we have a draft standard to point to.

markusicu
markusicu previously approved these changes Mar 27, 2025
@eggrobin eggrobin dismissed stale reviews from markusicu and macchiati via daa6098 March 27, 2025 17:52
@eggrobin eggrobin force-pushed the Other=ISO_Comment branch from daa6098 to 908d730 Compare March 27, 2025 17:53
@jira-pull-request-webhook
Copy link

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

@eggrobin eggrobin merged commit 1bf6bf7 into unicode-org:main Mar 28, 2025
15 checks passed
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