-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Ensure erased vals pass CheckRealizable #16111
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
natsukagami
merged 4 commits into
scala:main
from
natsukagami:4060-check-realizability-of-erased
Nov 8, 2022
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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 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 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
// See https://github.com/lampepfl/dotty/issues/4060#issuecomment-445808377 | ||
|
||
object App { | ||
trait A { type L >: Any} | ||
def upcast(erased a: A)(x: Any): a.L = x | ||
erased val p: A { type L <: Nothing } = p | ||
def coerce(x: Any): Int = upcast(p)(x) // error | ||
|
||
def coerceInline(x: Any): Int = upcast(compiletime.erasedValue[A {type L <: Nothing}])(x) // error | ||
|
||
trait B { type L <: Nothing } | ||
def upcast_dep_parameter(erased a: B)(x: a.L) : Int = x | ||
erased val q : B { type L >: Any } = compiletime.erasedValue | ||
|
||
def coerceInlineWithB(x: Any): Int = upcast_dep_parameter(q)(x) // error | ||
|
||
def main(args: Array[String]): Unit = { | ||
println(coerce("Uh oh!")) | ||
println(coerceInlineWithB("Uh oh!")) | ||
} | ||
} |
This file was deleted.
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.
Why is no error emitted on this line? What happens if I try to use
q
's bounds directly on the line below, without passing it as an argument to any function?I feel like realizability should be checked whenever we try to create an erased value.
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.
Realizability checks are always performed when bounds are used, so using
q
's bounds directly will CE even without this PR.This PR only adds the checks at function calls (they were performed at definition before, but they are not sufficient per the example).
I had a chat with @odersky about whether checks should be done when we create erased values. We concluded that it's okay to leave it at that to maximize flexibility of erased values.
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.
Ah. Then everything looks good to me.