Fix call signature caching #10703
Merged
Fix call signature caching #10703
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
|
thank you. |
Contributor
|
👍 can we add original repro as a test case (at least we'll be aware that something is not right if execution time of tests will significantly increase)? |
Member
Author
|
@vladima Sure, I'll add the original repro. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #10697. Previously we used
anySignatureboth as the signature foranyobjects and as a marker to indicate in-process resolution. This PR introduces a separateresolvingSignaturefor the latter case such that a result ofanySignatureis properly cached.