Disallow opaque type aliases of context functions #16041
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
We could allow them but they would not do what one probably expects (i.e. create context closures). This is because abstract types upper-bounded by context functions don't do that either (see neg/i16035a.scala), and we have to keep semantic equivalence between the two. Therefore, it's better to disallow them. Fixes scala#16035
som-snytt
reviewed
Sep 14, 2022
| def recur(tp: Type): Unit = tp.dealias match | ||
| case tp: HKTypeLambda => recur(tp.resType) | ||
| case tp if defn.isContextFunctionType(tp) => | ||
| report.error(em"context functon type cannot have opaque aliases", tree.srcPos) |
som-snytt
reviewed
Sep 14, 2022
| |CanThrow capabilities can only be generated $req.""", | ||
| pat.srcPos) | ||
|
|
||
| /** Check that tree does not define a context fucntion type */ |
Kordyjan
approved these changes
Sep 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
We could allow them but they would not do what one probably expects (i.e. create context closures). This is because abstract types upper-bounded by context functions don't do that either (see neg/i16035a.scala), and we have to keep semantic equivalence between the two.
Therefore, it's better to disallow them.
Fixes #16035