4.5.1. Bounded Wildcards

public void printList(List<? extends Number> list) { ... } // Upper bound

Upper bounded wildcards allow you to specify a type that can be any subtype of a particular class. In this case, List<? extends Number> means the method accepts a list of items that could be of type Number or any of its subclasses such as Integer, Double, etc. This allows for greater flexibility because it lets the method work with different types of Number while ensuring type safety.

Think of it like a recipe that requires an ingredient from a particular category, such as fruits. You can use any fruit from that category, like apples, oranges, or grapes, but they all belong to the broader category of 'fruit.' Similarly, in programming, upper bounded wildcards let your method work with any subclass of a specified type, ensuring the right type is always included.

public void addIntegers(List<? super Integer> list) { ... } // Lower bound

Lower bounded wildcards allow you to specify a type that can be any supertype of a particular class. Here, List<? super Integer> means you can pass a list that can accept Integer objects and any of its superclasses, such as Number or Object. This is useful when you want to add items to a collection but don’t need to know the specific type of that collection.

Imagine you’re organizing a school event and you need chairs. You can bring in any chair as long as it meets the minimum requirement of being a chair, regardless of whether it’s a folding chair, an office chair, or a lounge chair. In programming, lower bounded wildcards let you add elements to a collection where the collection can be of a type that is a supertype of the specified class, ensuring it can accept the newly added items.

Wildcards provide flexibility and type safety in APIs.

Wildcards in Java generics enhance your API's flexibility by allowing methods to operate on collections of various types without compromising type safety. Using wildcards helps in writing more generic and reusable code. This is particularly beneficial in methods where the exact type of collection elements may not be known ahead of time.

Consider a toolbox that includes different types of tools such as screwdrivers and wrenches. Instead of creating separate toolboxes for every kind of tool, you have one versatile toolbox that can accommodate various tools as long as they fit the generic description of a 'tool.' Similarly, wildcards allow your methods to accept many different types, simplifying code management and enhancing reusability.

--