Skip to content

feat(interfaces): getSuccessorForOperands in ControlFlowInterface - #1450

Open
axelcool1234 wants to merge 1 commit into
opencompl:mainfrom
axelcool1234:get-successor-for-operands
Open

axelcool1234 wants to merge 1 commit into
opencompl:mainfrom
axelcool1234:get-successor-for-operands

Conversation

@axelcool1234

Copy link
Copy Markdown
Collaborator

This will be replace getSuccessorForOperands? in DeadCodeAnalysis.lean.

@math-fehr

Copy link
Copy Markdown
Collaborator

Can you try to make this work like in HasOpInfo? So adding in HasOpInfo a field that would represent this. Then in each Dialect/OpInfo.lean file you add the implementation. So that the idea is that you can depend on ControlFlowInterface without depending on all dialects.

@axelcool1234
axelcool1234 force-pushed the get-successor-for-operands branch from 7c6e1a2 to 35dcdea Compare September 12, 2026 17:57
@axelcool1234

Copy link
Copy Markdown
Collaborator Author

Can you try to make this work like in HasOpInfo? So adding in HasOpInfo a field that would represent this. Then in each Dialect/OpInfo.lean file you add the implementation. So that the idea is that you can depend on ControlFlowInterface without depending on all dialects.

I believe I tried this and ran into an import dependency

@axelcool1234
axelcool1234 force-pushed the get-successor-for-operands branch from 35dcdea to e5a1f7d Compare September 12, 2026 19:14
@axelcool1234
axelcool1234 force-pushed the get-successor-for-operands branch from e5a1f7d to 676875f Compare September 15, 2026 02:46
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.

2 participants