Pattern matching remainders

[Izz Rainy]

Instead of having compilers potentially wrap the "true cause" of a failed
match in a MatchException, perhaps have MatchException be an interface
implemented by (subtypes of) ICCE and NPE, which compilers/runtimes and
future versions of the spec could add additional subtypes to later?

That way, exceptions thrown by matching would be consistent ("a subtype of
MatchException" rather than "an NPE or ICCE or ME"), and the spec would
have more flexibility to specify another top-level matching exception in
the future (and implementers could more easily specify their own diagnosis
logic) without breaking existing error handling, which also wouldn't have
to use an overly general catch block (catch all MEs and sometimes rethrow)
or parse exception descriptions (like a helpful-NPEs analogue) to rely a
more useful message to a developer or user.

Specifically using an interface would avoid needing to make all NPEs and
ICCEs into MatchExceptions (and potentially trigger false positive
catches), only producing match-based subtypes of these. Admittedly, that
relies on being able to specify a catch for an interface type with no
relation to Throwable, which may be too big of a change for consideration.