You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error:
bad constant pool tag 17 at byte 10172
while compiling: /Users/tisue/tmp/dotty-19527/S.scala
during phase: globalPhase=typer, enteringPhase=namer
...
at scala.tools.nsc.symtab.classfile.ClassfileParser$ConstantPool.errorBadTag(ClassfileParser.scala:411)
at scala.tools.nsc.symtab.classfile.ClassfileParser$ConstantPool.<init>(ClassfileParser.scala:230)
at scala.tools.nsc.symtab.classfile.ClassfileParser.$anonfun$parse$2(ClassfileParser.scala:173)
at scala.tools.nsc.symtab.classfile.ClassfileParser.$anonfun$parse$1(ClassfileParser.scala:159)
at scala.tools.nsc.symtab.classfile.ClassfileParser.parse(ClassfileParser.scala:142)
at scala.tools.nsc.symtab.SymbolLoaders$ClassfileLoader.doComplete(SymbolLoaders.scala:342)
at scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.$anonfun$complete$2(SymbolLoaders.scala:249)
...
The text was updated successfully, but these errors were encountered:
SethTisue
changed the title
"bad constant pool tag" when using a library compiled using Java 21
"bad constant pool tag 17" when using a library compiled using Java 21
Jan 25, 2024
this is the Scala 2 equivalent of scala/scala3#19527, reported against Scala 3 by @adamw yesterday
the original report has some information about what kind of bytecode is involved — it’s
switch
on certain types, e.g. Javaenum
sScala 2 reproducer:
result:
The text was updated successfully, but these errors were encountered: