Allow static reveal of instance function in new resolver #4733
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.
PR #4180 introduced the ability to
reveal
an instance function in a static context. In the recent PR #4498, this has been implemented to put the instance function itself, without a receiver argument, into an attribute. The recent PR then special-cases the resolution of that attribute. I would call that a hack.This PR mimics that hack for the new resolver. That makes
git-issue-4315.dfy
(see Issue #4315) pass with both resolvers.The hack introduced in this PR and in #4498 is not a great idea, because a use of
this
is placed into the AST in a context where there is nothis
. If (rather, when) this gets fixed, it should be fixed in both resolvers.How has this been tested?
Test
git-issues/git-issue-4315.dfy
has been converted to run with both the old and new resolver.By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.