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.
What's changed?
Add tests to show we ought to skip both Refaster (ok) and Class generics (not ok).
What's your motivation?
OrOrElseThrows is found in error-prone-support, but breaks template generation there due to a compilation error.
Anything in particular you'd like reviewers to focus on?
There's also the issue that the test template only works on Java 11.
I wonder if we should use that as minimum for rewrite-templating.
Have you considered any alternatives or workarounds?
Not quite sure yet how to catch and resolve this compilation error when using Java 11: