-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Kotlin: fix cases where type variables were used out of scope #9123
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
smowton
merged 14 commits into
github:main
from
smowton:smowton/fix/type-variable-in-scope-consistency
May 19, 2022
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
d291e0c
Fix typeParametersInScope consistency query
smowton b09b769
Extract type parameters without substituting their parent functions
smowton 048a530
Type parameter scoping check: distinguish type arguments from type pa…
smowton 102cdcd
Fix type substitution and source locations in SAM-converted generic i…
smowton 4e15f5f
Fix extracted type arguments of kotlin.jvm.functions.FunctionN
smowton 49c9c36
Type-variable-in-scope consistency query: account for all enclosing e…
smowton ada31f3
Distinguish result type parameter names
smowton 8a90dde
Accept test changes
smowton ea9aa59
Add test
smowton 4f54bb6
Accept consistency check failure
smowton e722c99
Autoformat
smowton 4f08981
Expand warning message to note that there are known Java extractor bu…
smowton 1039e29
Adjust test result
smowton c9232c0
Autoformat
smowton File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a test case for this? How come we didn't see this issue before? We have tests that cover big-arity functions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can add one -- I think we simply didn't notice or care that the type extracted was
FunctionN<FirstArgumentType>
notFunctionN<ReturnType>
. It's probably not a critical bug but rather a weird surprise waiting for someone down the line.