Java Development Kit (JDK) 16 has reached its preliminary rampdown part, that means the characteristic set is now frozen, as of December 10, 2020. The new options in JDK 16 vary from a second preview of sealed courses to sample matching to concurrent thread-stack processing for rubbish assortment.
JDK 16 would be the reference implementation of the model of normal Java set to observe JDK 15, which arrived September 15. A proposed launch schedule has JDK 16 reaching a second rampdown part on January 14, 2021, adopted by launch candidates arriving February four and February 18, 2021. The manufacturing launch is slated to be revealed March 16, 2021.
Seventeen proposals formally goal JDK 16 as of December 10, 2020. The new capabilities coming to Java 16 embody:
- The warnings for value-based courses proposal designates the primitive wrapper courses as value-based and deprecates their constructors for elimination, prompting new deprecation warnings. Warnings are supplied about improper makes an attempt to synchronize on cases of any value-based courses within the Java platform. Driving this effort is the Valhalla Project, which is pursuing a big enhancement to the Java programming mannequin within the type of primitive courses. Primitive courses declare cases to be identity-free and able to inline or flattened representations, the place cases might be copied freely between reminiscence places and encoded utilizing values of cases’ fields. The design and implementation of primitive courses in Java is now sufficiently mature that the migration of sure courses of the Java platform to primitive courses might be anticipated in a future launch. Candidates for migration are informally designated as value-based courses in API specs.
- Previously previewed in JDK 15, sealed courses and interfaces limit which different courses and interfaces could lengthen or implement them. Goals of the plan embody permitting the creator of a category or interface to manage the code liable for implementing it, present a extra declarative method than entry modifiers to limit the usage of a superclass, and help future instructions in sample matching by offering a basis for evaluation of patterns.
- Strong encapsulation of JDK internals by default, apart from crucial inner APIs comparable to
misc.Unsafe. Users can select the relaxed robust encapsulation that has been the default since JDK 9. Goals of this proposal embody bettering the safety and maintainability…
