Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting with scala.3.8, standard library will now be compiled with scala 3, instead of reusing scala 2 artifacts. This means that the way certain symbols are represented will change. For this project, we've run into an issue, where for:
scala 2 would generate a
<local child>symbol to assign to the child anonymous class, and scala 3 would intentionally reuse the parent symbol with the same goal - both behaviors are intended for pattern matcher to be able to give exhaustivity errors.In this fix here, we handle the scala 3 local child the same way we did for the scala 2 counterpart.
Related discussion: scala/scala3#24598