Expose typed OpenACC host fragments and remove deprecated parser API - #21
Conversation
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 08aeb62a06
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Swish! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
Summary
Why
REX must consume the parser's typed AST directly. Keeping the deprecated compatibility API would preserve two competing parser contracts and allow callers to bypass typed ownership. The new traversal API gives REX one explicit boundary for attaching frontend semantic nodes without reparsing or reconstructing host-language fragments later.
This is intentionally an API-breaking cleanup. Unsupported or malformed states are not projected through a fallback compatibility path.
Validation
git diff --check origin/main...HEADpassed