Scala 3: Erased context parameter before a normal one produces bytecode the JVM rejects
Fixed · medium · Crash
A method with an erased `using` parameter followed by a normal context parameter gets wrong local slot numbers, so the JVM throws VerifyError at runtime. The reversed order works.
Found: ; reported: ; status since: . Reporter: Mike Murunov
Page for this report · Public report · Fix or proposed fix (see status)
However, for erased parameters coming from a context-function(?), the erased parameter incorrectly remains in the tree after erasure.