Fix handling of recursive bounds in constraints #9012
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
These can lead to deep subtype errors, this also fixes scala#8976 but see also the next commit which fixes the underlying soundness issue.
`approximation` used to replace recursive occurences of the type variable being instantiated by `TypeBounds.empty`, but this is not sound in general since the approximation might be outside the bounds of the type variable. We could try to do something fancy with ApproximatingTypeMap but it seems complicated (and expensive) and there's an easier solution: since last commit, only the upper bound is allowed to be recursive, so we can just instantiate the type variable to its lower bound to avoid the problem in a sound and cheap way.
odersky
approved these changes
May 20, 2020
| if !constraint.contains(param) then true | ||
| else if !isUpper && param.occursIn(bound) | ||
| // We don't allow recursive lower bounds when defining a type, | ||
| // so we shouldn't allow them as constraints either. |
There was a problem hiding this comment.
I am not 100% sure about performance implications here. Let's test this.
|
test performance please |
|
Yes, that looks like a much better way to fix #8976 |
|
performance test scheduled: 1 job(s) in queue, 0 running. |
|
Performance test finished successfully: Visit http://dotty-bench.epfl.ch/9012/ to see the changes. Benchmarks is based on merging with master (43e4bfa) |
|
I think it's within the usual variance but we can run again to check |
|
test performance please |
|
performance test scheduled: 1 job(s) in queue, 0 running. |
|
Performance test finished successfully: Visit http://dotty-bench.epfl.ch/9012/ to see the changes. Benchmarks is based on merging with master (43e4bfa) |
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.
No description provided.