128-java-generics

To enforce compile-time type safety, you must eliminate raw types by refactoring Java source code to use parameterized types. This process replaces dangerous untyped collections with bounded type parameters, ensuring robust code and reducing runtime ClassCastException errors.

Apply the PECS principle—Producer Extends, Consumer Super—when designing generic APIs to maximize flexibility. Use extends wildcards for producers and super wildcards for consumers to ensure your generic utility classes accept both specific types and their subtypes seamlessly.

The best way to refactor a legacy collection utility class is to apply bounded type parameters and proper wildcards. This refactoring eliminates unnecessary casting, enforces strict compile-time type checking, and ensures the utility integrates seamlessly with specific types and their subtypes.

Yes, you can combine Java generics with modern features. Refactoring patterns provide specific integration methods for combining generics with Records, sealed types, and pattern matching to improve API flexibility and maintain strict type safety in modern Java projects.

Java generic code throws ClassCastException at runtime when raw types bypass compile-time type checking. Refactoring your code to implement type-safe generic patterns and enforce strict compile-time type safety eliminates these runtime errors and ensures robust code execution.