-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Incremental compilation and opaque types don't play nice together #13190
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
Comments
The example code fails separate compilation, but succeeds with joint compilation:
|
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Jul 30, 2021
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Jul 30, 2021
tanishiking
pushed a commit
to tanishiking/scala3
that referenced
this issue
Aug 10, 2021
smarter
pushed a commit
to dotty-staging/dotty
that referenced
this issue
Aug 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compiler version
3.0.1
Minimized code
fileA.scala
fileB.scala
Steps to reproduce
val f2: Int = f
f1
,f2
, and the summonOutput
Expectation
It should compile in both cases, also when using incremental compilation.
The text was updated successfully, but these errors were encountered: