Скачать или смотреть Understanding the Purpose of non-sealed Classes in Java's Sealed Class System

Explore the intriguing benefits of using `non-sealed` classes in Java 15's sealed class architecture. Discover how they provide flexibility in API design without compromising encapsulation.
---
This video is based on the question https://stackoverflow.com/q/63860110/ asked by the user 'Ayox' ( https://stackoverflow.com/u/4887297/ ) and on the answer https://stackoverflow.com/a/63887136/ provided by the user 'Brian Goetz' ( https://stackoverflow.com/u/3553087/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: What is the point of extending a sealed class with a non-sealed class?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
The Intriguing Role of non-sealed Classes in Java's Sealed Class System

Java 15 introduced a significant evolution in class design with the introduction of sealed classes, enabling developers to control which classes can extend others. However, the addition of the non-sealed keyword raises questions. One common query is: What is the point of extending a sealed class with a non-sealed class? Let's delve into this topic, unravel its intricacies, and understand why this design decision was made.

Understanding Sealed Classes

Sealed classes are a feature that allows API designers to specify which other classes are permitted to extend a particular class. This means that developers gain finer control over the inheritance hierarchy, ensuring that only known and carefully chosen subtypes are created.

Why Use Sealed Classes?

Controlled Inheritance: Keep the class hierarchy concise and manageable by limiting its extensions.

Enhanced Security: By restricting subclassing, sealed classes prevent misuse and unintended behavior that can often arise in open inheritance scenarios.

Exhaustive Pattern Matching: Ensures that switch statements and other control structures can safely assume that all possible subclasses have been accounted for.

The Role of non-sealed Classes

While you might think sealed classes should only permit final or other sealed classes as extensions, the non-sealed keyword serves a vital function. Here's why its introduction can make sense in real-world applications:

1. Allowing Specific Extension Points

In complex systems, there are situations where certain classes should remain extensible while others should not. The non-sealed class acts as an "escape hatch", providing flexibility to use custom extensions where necessary. For instance, in a command pattern implementation that provides specific commands, UserPluginCommand could be made non-sealed to allow user-defined implementations.

[[See Video to Reveal this Text or Code Snippet]]

2. Structured Extension Management

The use of a non-sealed class creates a well-defined pathway for subtypes. Instead of allowing random extensions, all new implementations funnel through the UserPluginCommand, ensuring there's an API designed specifically for extensibility. This way, developers can enhance the functionality while maintaining control over how those extensions interact with the overall design.

3. Confidence in Exhaustiveness

Even with an open-ended extension point like UserPluginCommand, the system can continue to leverage the sealed definition for its four known commands. Pattern matching can remain exhaustive:

[[See Video to Reveal this Text or Code Snippet]]

The above switch case remains safe and reliable because the core command classes are sealed, providing certainty about the behavior of the application.

Real-World Applications

An excellent example of non-sealed classes can be found in Java’s own packages, such as java.lang.constant, where it utilizes this model to facilitate extensibility through dynamic constants and dynamic call sites.

Conclusion

In conclusion, the non-sealed keyword in Java 15's sealed classes offers a sophisticated mechanism to balance control and flexibility in API design. By clearly defining extension points, it allows developers to create extensible classes in a structured and safe manner, minimizing the risks of uncontrolled subclassing while still enabling customizable implementations.

With this understanding, you can effectively integrate sealed and non-sealed classes in your Java applications, leveraging the power of controlled inheritance to achieve robust and maintainable code.