> Currently, an enum switch with patterns is desugared in a very non-standard, > and potentially slow, way. It would be better to use the standard > `typeSwitch` bootstrap to classify the enum constants. The bootstrap needs to > accept enum constants as labels in order to allow this. A complication is > that if an enum constant is missing, that is not an incompatible change for > the switch, and the switch should simply work as if the case for the missing > constant didn't exist. So, the proposed solution is to have a new bootstrap > `enumSwitch` that accepts `String`s in place of the enum constants, and will > internally convert them to the appropriate enum constants, and then it will > find the proper case similarly to `typeSwitch`. > > How does this look?
Jan Lahoda has updated the pull request incrementally with one additional commit since the last revision: If the pattern type is a supertype of the selector type, use selector type rather than the pattern type when constructing the bootstrap method parameters. ------------- Changes: - all: https://git.openjdk.java.net/jdk17/pull/81/files - new: https://git.openjdk.java.net/jdk17/pull/81/files/469254a4..d970402e Webrevs: - full: https://webrevs.openjdk.java.net/?repo=jdk17&pr=81&range=07 - incr: https://webrevs.openjdk.java.net/?repo=jdk17&pr=81&range=06-07 Stats: 30 lines in 2 files changed: 27 ins; 0 del; 3 mod Patch: https://git.openjdk.java.net/jdk17/pull/81.diff Fetch: git fetch https://git.openjdk.java.net/jdk17 pull/81/head:pull/81 PR: https://git.openjdk.java.net/jdk17/pull/81
