As the ear hit eardrums “overriding” we quickly get to know that it can be done either virtue of different datatypes or arguments passed to a function what a programmer learned initially while learning polymorphism in java. Before JDK 5.0, it was not possible to override a method by changing the return type. When we override a parent class method, the name, argument types, and return type of the overriding method in child class has to be exactly the same as that of the parent class method. The overriding method was said to be invariant with respect to return type.
Java version 5.0 onwards it is possible to have different return types for an overriding method in the child class, but the child’s return type should be a subtype of the parent’s return type. The overriding method becomes variant with respect to return type.
The co-variant return type is based on the Liskov substitution principle.
Now geeks you must be wondering about why to use for which we will be listing down the advantages as follows:
- It helps to avoid confusing type casts present in the class hierarchy and thus making the code readable, usable and maintainable.
- We get the liberty to have more specific return types when overriding methods.
- Help in preventing run-time ClassCastExceptions on returns
Note: If we swap return types of Base and Derived, then above program would not work. Please see this program for example.
Example Two classes used for return types
Java
class A {
}
class B extends A {
}
class Base {
A fun()
{
System.out.println( "Base fun()" );
return new A();
}
}
class Derived extends Base {
B fun()
{
System.out.println( "Derived fun()" );
return new B();
}
}
public class GFG {
public static void main(String args[])
{
Base base = new Base();
base.fun();
Derived derived = new Derived();
derived.fun();
}
}
|
Output:
Base fun()
Derived fun()
This article is contributed by Gaurav Miglani. If you like GeeksforGeeks and would like to contribute, you can also write an article using write.geeksforgeeks.org or mail your article to review-team@geeksforgeeks.org. See your article appearing on the GeeksforGeeks main page and help other Geeks. Please write comments if you find anything incorrect, or you want to share more information about the topic discussed above.