Skip to content

Validate partial name pattern persistence - #17

Draft
1sgtpepper wants to merge 2 commits into
validation-pr633-basefrom
validation-template-state-property
Draft

Validate partial name pattern persistence#17
1sgtpepper wants to merge 2 commits into
validation-pr633-basefrom
validation-template-state-property

Conversation

@1sgtpepper

@1sgtpepper 1sgtpepper commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Fork-only validation spike for PR project-llzk#633 design work.

Checks whether a generic segmented poly.name_pattern operation attribute:

  • preserves the existing C and C++ builder calls;
  • round-trips through text and bytecode without a custom schema or version hook;
  • survives generic cloning; and
  • builds across the repository CI matrix.

This is not intended for upstream merge.

@1sgtpepper
1sgtpepper force-pushed the validation-template-state-property branch 7 times, most recently from 0e9ddfc to 6427050 Compare July 28, 2026 13:09
@1sgtpepper
1sgtpepper force-pushed the validation-template-state-property branch from 6427050 to 0ec9a2c Compare July 28, 2026 13:24
@1sgtpepper 1sgtpepper changed the title Validate template state property storage Validate partial name pattern persistence Jul 28, 2026
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