-
-
Notifications
You must be signed in to change notification settings - Fork 436
Separate patching phases for patchers that require multiple passes. #659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or 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
Maybe it makes sense to add a test for this use case. |
Rebased and added a test to catch if patchers are run more times than expected. I verified that the test fails without the other fixes. |
…rently only need for Operator overloading). This patcher phase is run after other patchers.
…patching phases is erroneously applying the patcher multiple times.
I will re-review this PR =) |
It took me some time, but finally merged. I will release v1.17 soon. |
SimFG
pushed a commit
to SimFG/expr
that referenced
this pull request
Apr 15, 2025
…xpr-lang#659) * Reset tracking of applied operator overloads before every walk of the ast tree. * Remove limit on operator overload resolution * Do separate patcher phase for those that require multiple passes (Currently only need for Operator overloading). This patcher phase is run after other patchers. * Add test to track how many times a patcher is run. Used to detect if patching phases is erroneously applying the patcher multiple times. --------- Co-authored-by: Anton Medvedev <[email protected]>
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.
See issue #637
This contains the changes from pull request #658 as well. If this pull is accepted that one may be closed.
Commit 3da8527 introduced repeating the patch phase for operator overloading, but also reruns all patchers any time an operator overload is patched.
This can break patchers that don't expect to be re-run over the statement multiple times.
This patch set splits patching into two phases. First phase only patchers that don't require multiple passes are run. Second phase only patchers that require multiple passes are run.
As a side effect, it also allows any ordering between other patchers and operator overloads, where as previously if a patcher changed a nodes type it would have to be supplied as an option before the operator.
Passes all tests.