Don't interpolate downwards to Nothing #7130
Closed
Conversation
This file contains 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
odersky
added a commit
to dotty-staging/dotty
that referenced
this pull request
Aug 29, 2019
If the result of a covariant type variable interpolation would be a bottom type,
wait instead. This could make the variable be inferred to its upper bound after all,
if we do not need a fully instantiated type right away.
This makes a difference for indentation whereever we have a situation like this:
```
def foo: T =
bla.asInstanceOf
```
With indentation on, this is now equivalent to
```
def foo: T = {
bla.asInstanceof
}
```
This means there is now an added opportunity for an interpolation step, of
the asInstanceOf, which would go downwards to Nothing. So indentation changes
the inferred type, which is very bad. With the commit the problem is
avoided.
The commit is broken out separately into PR scala#7130.
odersky
added a commit
to dotty-staging/dotty
that referenced
this pull request
Aug 29, 2019
If the result of a covariant type variable interpolation would be a bottom type,
wait instead. This could make the variable be inferred to its upper bound after all,
if we do not need a fully instantiated type right away.
This makes a difference for indentation whereever we have a situation like this:
```
def foo: T =
bla.asInstanceOf
```
With indentation on, this is now equivalent to
```
def foo: T = {
bla.asInstanceof
}
```
This means there is now an added opportunity for an interpolation step, of
the asInstanceOf, which would go downwards to Nothing. So indentation changes
the inferred type, which is very bad. With the commit the problem is
avoided.
The commit is broken out separately into PR scala#7130.
odersky
changed the title
If the result of a covariant type variable interpolation would be a bottom type, wait instead. This could make the variable be inferred to its upper bound after all, if we do not need a fully instantiated type right away.
odersky
force-pushed
the
fix-interpolation
branch
from
419d232
to
119752f
Compare
odersky
added a commit
to dotty-staging/dotty
that referenced
this pull request
Aug 29, 2019
If the result of a covariant type variable interpolation would be a bottom type,
wait instead. This could make the variable be inferred to its upper bound after all,
if we do not need a fully instantiated type right away.
This makes a difference for indentation whereever we have a situation like this:
```
def foo: T =
bla.asInstanceOf
```
With indentation on, this is now equivalent to
```
def foo: T = {
bla.asInstanceof
}
```
This means there is now an added opportunity for an interpolation step, of
the asInstanceOf, which would go downwards to Nothing. So indentation changes
the inferred type, which is very bad. With the commit the problem is
avoided.
The commit is broken out separately into PR scala#7130.
i536.scala previously compiled since the type argument was inferred to be Nothing. But that inference is useless; it just hides a runtime failure. The issue scala#536 only complained that the compiler crashed, so having a negative outcome is permissible.
odersky
added a commit
to dotty-staging/dotty
that referenced
this pull request
Aug 29, 2019
This was referenced Aug 29, 2019
odersky
added a commit
to dotty-staging/dotty
that referenced
this pull request
Aug 29, 2019
|
This was merged as part of #7114 |
odersky
added a commit
to dotty-staging/dotty
that referenced
this pull request
Sep 3, 2019
Undo the change where we do not interpolate a type variable if its lower bound is nothing. It turned out this broke type inference.
odersky
added a commit
to dotty-staging/dotty
that referenced
this pull request
Sep 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If the result of a covariant type variable interpolation would be type Nothing,
wait instead. This could make the variable be inferred to its upper bound after all,
if we do not need a fully instantiated type right away.