-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Regression in match exhaustivity of higher-kinded types #17230
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
This issue was picked for the Issue Spree No. 29 of 18 April 2023 which takes place in a week from now. @dwijnand, @natsukagami, @TheElectronWill, @XLPI will be working on it. If you have any insight into the issue or guidance on how to fix it, please leave it here. |
Minimised trait Foo:
type Bar[_]
object Foo:
type Aux[B[_]] = Foo { type Bar[A] = B[A] }
class Test:
def test[B[_]](self: Option[Foo.Aux[B]]) = self match
case Some(b) => 1
case None => 2 |
Guys, is anybody continue to work on this issue? How actually our workflow in Compiler Academy is should going? @scala-center-bot |
I re-assigned you to work on this with Dale during next spree. Is that okay with you? |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Please ignore the 2 previous message from the Scala Center bot. Teams for the next spree can be found here: https://airtable.com/shrSni1OItSuErosU/tblLEWc2ISeGHPbsc. Sorry for the spam! |
What is the current status of this issue? It has been investigated during 2 sprees; what were the conclusions? |
If I remember correctly, it's due to a difference in how type variables are instantiated in the Space engine. I'll got this on my list to come back to. |
Compiler version
3.3.1-RC1-bin-20230407-bcaa1ca-NIGHTLY
Minimized code
Based on Open CB failure https://github.com/VirtusLab/community-build3/actions/runs/4650721329/jobs/8230332752 for rescala-lang/rescala
Output
Expectation
Should not give warning
The text was updated successfully, but these errors were encountered: