fix(regex): retain safe ASCII-strict fold siblings - #1072
Open
fglock wants to merge 1 commit into
Open
Conversation
Keep non-ASCII fold siblings available when Perl ASCII-strict matching protects a source character from fold alternatives that cross into ASCII. Generated with [OpenAI Codex](https://openai.com/codex) Co-Authored-By: OpenAI Codex <codex@openai.com>
fglock
marked this pull request as ready for review
August 18, 2026 22:06
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
1 participant
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.
Summary
/aaValidation
make: 595 tests, exit 0, 4m33sScope
This is a stacked Phase 36 delivery based on
fix/phase36-joni-branch-reset-calls-v2.The follow-up ordinary negative-class and class-intersection slices remain separate.