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
In Java 17, released a few days ago, sealed classes officially become a feature. It seems this library is a good place to support the functionality of adding more permitted subclasses to a sealed class (or destroy the seal altogether), since sealed class status is described together with being final, both as restrictions on inheritance.
Note: in practice, this may be less useful because the permitted subclasses must be in the same package (in an unnamed module) or in the same named module. Since Minecraft distributions run as unnamed modules, it may be interesting to see their usage of sealed classes once they update to Java 17 (little reason not to do so as 17 is a LTS release)
The text was updated successfully, but these errors were encountered:
In Java 17, released a few days ago, sealed classes officially become a feature. It seems this library is a good place to support the functionality of adding more permitted subclasses to a sealed class (or destroy the seal altogether), since sealed class status is described together with being final, both as restrictions on inheritance.
Note: in practice, this may be less useful because the permitted subclasses must be in the same package (in an unnamed module) or in the same named module. Since Minecraft distributions run as unnamed modules, it may be interesting to see their usage of sealed classes once they update to Java 17 (little reason not to do so as 17 is a LTS release)
The text was updated successfully, but these errors were encountered: