BE-304: HashQL: Terminator placement based on capabilities#8359
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
PR SummaryMedium Risk Overview Transfer costs are derived from liveness + per-local Written by Cursor Bugbot for commit 3927741. This will update automatically on new commits. Configure here. |
2f02bbc to
d1d3e0b
Compare
d25735c to
c40fc37
Compare
Your organization requires reapproval when changes are made, so Graphite has dismissed approvals. See the output of git range-diff at https://github.com/hashintel/hash/actions/runs/22184745507
c40fc37 to
bfb276b
Compare
d1d3e0b to
7554ef3
Compare
7554ef3 to
719e74b
Compare
Merge activity
|
719e74b to
3927741
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
🌟 What is the purpose of this PR?
Adds terminator placement analysis to the MIR execution planning pipeline. This complements statement placement by analyzing control flow edges rather than individual statements, determining which backend transitions are valid at each edge and their associated transfer costs.
🔍 What does this change?
Pre-Merge Checklist 🚀
🚢 Has this modified a publishable library?
This PR:
📜 Does this require a change to the docs?
The changes in this PR:
🕸️ Does this require a change to the Turbo Graph?
The changes in this PR:
🛡 What tests cover this?