jextract/jni: Use switch expressions in getCase()#717
Merged
ktoso merged 1 commit intoswiftlang:mainfrom Apr 22, 2026
Merged
Conversation
ktoso
approved these changes
Apr 22, 2026
Collaborator
|
Oh wait... which java source version does this require... |
Contributor
Author
|
It became available in Java 14, and given the current use of sealed classes, I believe this is perfectly acceptable. |
Collaborator
|
Sweet, I was just checking now -- 14 is perfectly fine :-) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Using a switch expression for the
Case getCase()implementation makes the code cleaner.Since switch expressions are exhaustive, it eliminates the need to throw a
RuntimeException.