ToTreeless: allow backends to define custom pipelines #7273
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
UlfNorell
approved these changes
May 16, 2024
omelkonian
force-pushed
the
orestis/custom-treeless
branch
from
b9ec011
to
daaa216
Compare
omelkonian
force-pushed
the
orestis/custom-treeless
branch
from
daaa216
to
142a4cf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When developing backends, the translation from internal syntax to treeless syntax currently only exports
toTreelesswith a fixed pipeline of optimization passes (compilerPipeline).This PR introduces
toTreelessWithto allow backends to tweak that and use a custom pipeline (I already need that in agda2rust), while also exporting necessary utilities to build those pipelines.