Skip to content

fix: decline unclosed function views without crashing repair callers - #2

Merged
RetroGameDeveloper merged 1 commit into
mainfrom
fix/unclosed-flow
Nov 13, 2026
Merged

RetroGameDeveloper merged 1 commit into
mainfrom
fix/unclosed-flow

Conversation

@RetroGameDeveloper

Copy link
Copy Markdown
Contributor

An unmatched closing brace in a simplified function view made local_flow.Flow subtract from None. Existing callers only catch ValueError/RecursionError for unsupported syntax, so this escaped conversion scheduling and killed the app permuter thread.

Check the closing boundary explicitly and raise the existing unsupported-syntax ValueError. Public liveness, branch-call facts and conversion scheduling then give no advice for that view. Valid closed functions keep their liveness facts. This includes valid C whose alternative preprocessor opening braces become unmatched when directives are blanked; no C or matching verdict is changed.

Validation: three malformed/conditional-view regressions fail with TypeError before the change; all four new controls and the full 96-test library suite pass afterward. Ruff and diff checks pass. Bump the patch version to 0.2.1 for the consuming app. Synthetic fixtures only; no game data, compiler runs or model calls.

@RetroGameDeveloper
RetroGameDeveloper merged commit 16d8b50 into main Nov 13, 2026
1 check 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.

1 participant