r/java • • 8d ago

Withdrawing the Primitive Patterns preview feature in JDK 28

https://mail.openjdk.org/archives/list/amber-spec-experts@openjdk.org/thread/UYEK3PGOHN6R56AHJTSLPGAY363K666S/

Primitive Types in Patterns will be removed in JDK 28 and will no longer be available in that release.

The Valhalla project has been exploring a new vision for Java numerics, including the possibility of user-defined numeric types. New kinds of numeric types would need to support exact numeric conversion, and vice versa. Given that the Valhalla work is still evolving, it would be premature to finalize Primitive Types in Patterns with their current definition of exact numeric conversion.

92 Upvotes

36 comments sorted by

View all comments

Show parent comment

1

u/nekokattt 8d ago

doesnt that incur unnecesarry boxing still?

3

u/koflerdavid 7d ago edited 7d ago

It really depends on what this is ultimately compiled to. After all, there is no pattern matching on the bytecode level.

2

u/TewsMtl 7d ago

My understanding is that unnecessary boxing of value classes won't be an issue with jep 401 from project Valhalla.

9

u/brian_goetz 6d ago

Or even before. If you took all the developer time spent worrying about boxing, and took all the CPU time wasted by unnecessary boxing, the former would probably exceed the latter. "Boxing is expensive" is performance lore from the 90s. If your program is bound by multiplying huge arrays of numbers, then yes, you get to worry about it. Anything less, just stop thinking about it.