-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
regression: crash when summoning type equivalence #18650
Labels
Comments
p-pavel
added
itype:bug
itype:crash
stat:needs triage
Every issue needs to have an "area" and "itype" label
labels
Oct 4, 2023
bishabosha
added
area:typer
and removed
stat:needs triage
Every issue needs to have an "area" and "itype" label
labels
Oct 16, 2023
I added the correct stack trace |
minimized to: //> using scala 3.3.1
class Church[A]():
type F[_]
type Nat = F[(A => A) => (A => A)]
given makeChurch[A]: Church[A] = ??? // necessary to cause crash
@main
def churchTest =
val c: Church[Int] = ???
summon[c.Nat =:= ((Int => Int) => (Int => Int))] |
bishabosha
added
the
regression
This worked in a previous version but doesn't anymore
label
Oct 16, 2023
in 3.3.0 there was no crash, however there was still a type error. It seems the crashing assertion is to check in |
bishabosha
changed the title
Compiler crash when trying to summon type equivalence
regression: crash when summoning type equivalence
Oct 16, 2023
odersky
added a commit
that referenced
this issue
Oct 19, 2023
odersky
added a commit
that referenced
this issue
Dec 17, 2023
Using issue #18650 as the reference (but issue #18999 is another option) building on the fix in PR #18719 (refined in PR #18727) as well as the fix in PR #18760, I'm trying to make a more root change here by making sure that message forcing only occurs with `hasErrors`/`errorsReported` is true, so as to avoid assertion errors crashing the compiler.
dwijnand
pushed a commit
to dwijnand/scala3
that referenced
this issue
Feb 21, 2024
Using issue scala#18650 as the reference (but issue scala#18999 is another option) building on the fix in PR scala#18719 (refined in PR scala#18727) as well as the fix in PR scala#18760, I'm trying to make a more root change here by making sure that message forcing only occurs with `hasErrors`/`errorsReported` is true, so as to avoid assertion errors crashing the compiler. (cherry picked from commit 10f2c10)
dwijnand
pushed a commit
to dwijnand/scala3
that referenced
this issue
Mar 5, 2024
Using issue scala#18650 as the reference (but issue scala#18999 is another option) building on the fix in PR scala#18719 (refined in PR scala#18727) as well as the fix in PR scala#18760, I'm trying to make a more root change here by making sure that message forcing only occurs with `hasErrors`/`errorsReported` is true, so as to avoid assertion errors crashing the compiler. (cherry picked from commit 10f2c10)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Compiler version
3.3.1
Minimized code
I know the code may look a bit strange, but this is what I could reproduce:
Output
Stack trace
The text was updated successfully, but these errors were encountered: