Less redundancy!

JEP 375: Pattern Matching for instanceof (Second Preview) – Updated

Chris Stewart

It’s the little things that make the difference in life. And since time – especially for developers – is money, unnecessary and redundant tasks should be avoided where possible. With this in mind, JEP 375 continues what was started with JEP 305 – the introduction of pattern matching to Java.

Update – May 4, 2020

Since this article originally appeared, there have been some changes made to JEP 375. It was previously intended for this second preview to incorporate enhancements based on user feedback received since the first preview in JDK 14. However, on April 14, Gavin Bierman wrote the following in the amber-spec-experts mailing list:

We have decided to remove the deconstruction patterns for record types from this preview release. There are some complications surrounding generics and deconstruction patterns, along with varargs and deconstruction patterns, and we’d like some more time to consider our design. I’ll write separately on these issues.

Elsewhere, in the JDK Bug System on the JEP 375 issue page, he further stated, “we are not adding any enhancements for this preview. We have many enhancements planned for the future, although they may come in other JEPs.” So for the moment, JEP 375 becomes a straightforward second round of the preview that took place in Java 14, and any new enhancements will take the form of new JDK enhancement proposals (JEPs).

Thanks for reading this update! To stay in the loop, keep an eye on the latest Java 15 news with us.


Original article – March 19, 2020

For project Amber, work is being done on pattern matching for Java, among other things. For the instanceof operator, pattern matching in Java 14 will soon become a reality. In JEP 305 – Pattern Matching for instanceof (Preview), Brian Goetz explains that pattern matching should make the Java programming language more concise and secure.

A so-called pattern is basically nothing more than a combination of a predicate for a certain target structure and a series of matching variables. If hits for the variables occur during the execution of the application, they are assigned suitable contents. The “form” of objects can thus be precisely defined, after which they are then tested by statements and expressions against their own input.

If only one type of pattern was proposed in JEP 305 (Type Test Pattern), the second preview, which was proposed as JEP 375 – Pattern Matching for instanceof (Second Preview) for JDK 15, still has the Deconstruction Pattern on board. The Type Test Pattern consists of the above predicate, which specifies a type, and a single binding variable. The Deconstruction Pattern consists of a predicate specifying a record type and several binding variables for the components of the record type.

SEE ALSO: Java 14: All the new features of JDK 14 as it hits GA

The use of pattern matching in instanceof could reduce the number of type conversions required in Java applications. In future Java versions, pattern matching could be used for further language constructs such as switch expressions.

As always, further information can be found on the OpenJDK website. Additionally, if you want to see this feature in action, check out this deep dive into pattern matching.

Chris Stewart
Chris Stewart is an Online Editor for He studied French at Somerville College, Oxford before moving to Germany in 2011. He speaks too many languages, writes a blog, and dabbles in card tricks.

Inline Feedbacks
View all comments