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
bug got recognized and marked as wontfix - it's not a big issue as it only affects testing with compileErrors, but we'll leave the note here to explain why we'll have to keep supporting a few tests disabled for Scala 3 only
MateuszKubuszok
changed the title
Known, relevant and unresolved/undocumented in Chimney compiler bugs
Compiler bugs: known, relevant and unresolved/undocumented
May 8, 2024
This ticket is intended to be a pinned list of compiler bugs that:
Documented fixes can be found in the latest version of troubleshooting section.
Compiler bugs
Position.point on NoPosition when using: macro implicit, Wmacros:both and Xlint:unused scala/bug#12895 - reported as a bug in Chimney in java.lang.UnsupportedOperationException: Position.point on NoPosition in chimney 0.8.0 #411- documentedchildren queried before class was discovered
error when typeCheckErrors is used scala/scala3#18484 - found during 0.8.x development, makes it hard to test whether Scala 3 matches Scala 2 behavior when it comes to detecting subtype names ambiguities (tests are ignored on Scala 3 for now)wontfix
- it's not a big issue as it only affects testing withcompileErrors
, but we'll leave the note here to explain why we'll have to keep supporting a few tests disabled for Scala 3 onlyMisbehavior of macro-generated match when matching case object with lowercase name scala/scala3#20350 - reported as a bug in Chimney in ClassCastException thrown on Scala 3 when transforming sealed traits to Protobuf GeneratedEnum #479- after all it was a bug in Chimney although it was hard to diagnose, fixed in Fix ClassCastException for lowercase objects in Scala 3 #603A <: GeneratedSealedOneOf with Singleton
) not picked up by a macro on Scala 3, it might be a bug in Chimney, but for now we have to consult the compiler teamThe text was updated successfully, but these errors were encountered: