Mark match that is unchecked by Scala 2 as unchecked #3190
Merged
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.
The Dotty exhaustivity checker is both smarter and more demanding than Scala 2's, and this is a case where it warns while Scala 2 just silently ignores the fact that it can't prove exhaustivity (it's the only case like this in cats-core).
It would be possible to make the match exhaustive in a way that both compilers would accept by writing something like this:
…but that results in an extra
ArrayBuffer
instantiation in the empty case. Adding@unchecked
seems to me like a reasonable fix, since it just flags what the Scala 2 compiler is already doing.