-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Introduce ExpressionRef
#5644
Closed
Closed
Introduce ExpressionRef
#5644
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
This was referenced Jul 10, 2023
Current dependencies on/for this PR: This comment was auto-generated by Graphite. |
MichaReiser
force-pushed
the
pass-format-context-to-needs-parentheses
branch
from
July 10, 2023 12:09
738e9a9
to
2c04bdc
Compare
MichaReiser
force-pushed
the
expression-ref
branch
from
July 10, 2023 12:10
42ada26
to
32813bd
Compare
PR Check ResultsEcosystem✅ ecosystem check detected no changes. BenchmarkLinux
Windows
|
MichaReiser
force-pushed
the
pass-format-context-to-needs-parentheses
branch
from
July 11, 2023 06:57
2c04bdc
to
0681c5e
Compare
MichaReiser
force-pushed
the
expression-ref
branch
from
July 11, 2023 06:57
32813bd
to
9cc7c21
Compare
konstin
approved these changes
Jul 11, 2023
MichaReiser
force-pushed
the
pass-format-context-to-needs-parentheses
branch
from
July 11, 2023 11:30
0681c5e
to
c895628
Compare
MichaReiser
force-pushed
the
expression-ref
branch
from
July 11, 2023 11:30
9cc7c21
to
f3444d0
Compare
MichaReiser
force-pushed
the
pass-format-context-to-needs-parentheses
branch
from
July 11, 2023 12:20
c895628
to
553008e
Compare
Base automatically changed from
pass-format-context-to-needs-parentheses
to
main
July 11, 2023 12:28
MichaReiser
force-pushed
the
expression-ref
branch
from
July 11, 2023 12:33
f3444d0
to
71a59d1
Compare
Closing for now as it isn't needed right way. We can reconsider adding |
This was referenced Aug 16, 2023
charliermarsh
added a commit
that referenced
this pull request
Aug 17, 2023
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.
Summary
Same as for the previous PR. I assumed that I would need to match on all
Expr
and this isn't easily possible withAnyNodeRef
.That's why I introduced a new
ExpressionRef
which is the unowned pendant toExpr
. There are a few cases where it allows me to remove some debug assertions, but I didn't end up using it heavily.We can merge it if you find it useful, or leave it as is.
Test Plan
It compiles