Skip to content

fix(regex): integrate ASCII-strict safe siblings - #1073

Draft
fglock wants to merge 1 commit into
integration/phase36-native-syntax-v2from
integration/phase36-native-syntax-v3
Draft

fix(regex): integrate ASCII-strict safe siblings#1073
fglock wants to merge 1 commit into
integration/phase36-native-syntax-v2from
integration/phase36-native-syntax-v3

Conversation

@fglock

@fglock fglock commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Summary

  • integrate the validated Perl ASCII-strict safe-sibling Joni patch
  • retain exact source matching while preserving all-non-ASCII fold alternatives
  • keep the negative-class and class-intersection follow-ups isolated

Validation

  • worker canonical Perl reducer: 14/14
  • worker direct Joni focused/combined gates: 12/12
  • combined warning-free make: 595 tests, exit 0, 3m46s
  • git range-diff confirms the worker commit transplanted unchanged

Stack

This one-commit WIP is based on integration/phase36-native-syntax-v2 and is
part of the forward-only Phase 36 Joni migration.

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>
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.

1 participant