Replies: 2 comments
-
The reason is that they are various case classes implementing that trait and we need to pattern match exhaustively on them. Note that this trait actually disappears in the next major version of specs2 to simply use |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for the reply. Guess there's some refactoring coming up here |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm currently in the process of upgrading a code base which has some non-test code extending and using
MatchResult
directly. Just wondering if there was any specific reason why the traitMatchResult
ended up being sealed (besides preventing what I encountered 😏 )?Beta Was this translation helpful? Give feedback.
All reactions