Expression switch exception naming

[Liam Miller-Cushon]

On Fri, Mar 30, 2018 at 11:40 AM Brian Goetz <brian.goetz at oracle.com> wrote:

>   - We'd additionally consider an expression switch to be exhaustive if
> all known enums are present _and_ the enum type is in the same module as
> the switch
>
> But that's probably too fussy.
>

I think it would be surprising for this to depend on where the declaration
of the
enum was located.

Treating expression switches that handle all constants of an enum as
exhaustive might be most valuable across compatibility boundaries. If the
enum is declared nearby, adding a method to the enum is often a good
alternative to switching on it. When switches are used to associate
behaviour with enums in other libraries that can't be modified directly,
having
a way to ensure those switches are updated if values are added to the enum
eliminates a category of bugs.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/amber-spec-experts/attachments/20180330/d400c50f/attachment-0001.html>