You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not yet sure if this is merely the first, or the only adjustment we'll have to make. If it's the only change then we can look to do something similar as we did for Java 23, to support that using our existing Java 21 parser.
If we expect more changes, then it might make sense to fork the Java 21 parser and start a Java 24 parser without these removed type references. The best time to fork the Java 21 parser is likely after we add Lombok & JEP-440 & JEP-441 support there. Getting the timing right ensures there's less work to maintain those forks in parallel as we build out their capabilities. Lombok support is already in our Java 17 parser; these PRs track further additions to our parsers
In JDK 24 per this commit in October (Respective PR) the
Type.UnknownType
has been removed, and its usage has been swapped out withType.ErrorType
.Example stacktrace:
The text was updated successfully, but these errors were encountered: