If you have just started the exploration of .Net Framework 4.0, two terms namely Covariance and Contravariance might have been heard. The concept that these terms encapsulate are used by most developer almost daily, however there has never been any botheration about the terminologies.
Now, what actually these terms mean and how are these going to affect us as a developer, if we dive in to the details. The simple answer is it’s always good to know your tools before actually using them.
Enough philosophy, let’s get to the business.
Starting the discussion let me reiterate that in addition to Covariance and Contravariance, there is another terminology, Invariance. I’ll by start here by diving into the details of Invariance and then proceed further.
Invariance:
Invariance can be better understood by considering the types in .Net.>net has basically two type, value-types and reference-types. Value types (int, double etc) are invariant i.e. the types can’t be interchanged either at assignment or as passing values to the parameters.
For example if the expected value is an array of integers (int []), and we try to pass an array of doubles (double []), this will definitely result in error.
(Please Note: some types of higher order may be used in place of lower order while assigning values or passing parameters to a function)
Variant
A type must be a sub-type for another type to be a variant. Variant, as the name suggests is something that can vary. Let’s consider reference Types in .Net. All reference types ultimately derive from System.Object.
As we said in the beginning any subtype of a base type can act as variant.
How does a reference type behave as variant?
When a subtype is used in place of a base type (string in place of an object), an implicit conversion takes place and is legally acceptable.
Variant has two sub-categories
1. Covariance
2. Contra-variance
Covariance:
Covariant involves being able to use a more derived type as a substitute, e.g. a string in place of an object. Let’s consider an example to prove this.
string[] a = new string[1];
object[] b = a;
Response.Write(b[0]);
String is a sub-type of an object type and hence the code works fine with no error.
Covariance is applicable not only for assignments but also for return types from methods. It permits a method to have a more derived return type than what is defined in the delegate.
Contra-variance:
Contra-variance is just the opposite(rather juxtaposition image) of variance.In this, more specific can be used in place of derived types
Please visit the link to see a working example.
Following are the links that can be helpful in understanding the topic better.
Link1:
Link2:
Link3:
Hope this was Helpful.
Till next time we connect…Happy Coding.
Now, what actually these terms mean and how are these going to affect us as a developer, if we dive in to the details. The simple answer is it’s always good to know your tools before actually using them.
Enough philosophy, let’s get to the business.
Starting the discussion let me reiterate that in addition to Covariance and Contravariance, there is another terminology, Invariance. I’ll by start here by diving into the details of Invariance and then proceed further.
Invariance:
Invariance can be better understood by considering the types in .Net.>net has basically two type, value-types and reference-types. Value types (int, double etc) are invariant i.e. the types can’t be interchanged either at assignment or as passing values to the parameters.
For example if the expected value is an array of integers (int []), and we try to pass an array of doubles (double []), this will definitely result in error.
(Please Note: some types of higher order may be used in place of lower order while assigning values or passing parameters to a function)
Variant
A type must be a sub-type for another type to be a variant. Variant, as the name suggests is something that can vary. Let’s consider reference Types in .Net. All reference types ultimately derive from System.Object.
As we said in the beginning any subtype of a base type can act as variant.
How does a reference type behave as variant?
When a subtype is used in place of a base type (string in place of an object), an implicit conversion takes place and is legally acceptable.
Variant has two sub-categories
1. Covariance
2. Contra-variance
Covariance:
Covariant involves being able to use a more derived type as a substitute, e.g. a string in place of an object. Let’s consider an example to prove this.
string[] a = new string[1];
object[] b = a;
Response.Write(b[0]);
String is a sub-type of an object type and hence the code works fine with no error.
Covariance is applicable not only for assignments but also for return types from methods. It permits a method to have a more derived return type than what is defined in the delegate.
Contra-variance:
Contra-variance is just the opposite(rather juxtaposition image) of variance.In this, more specific can be used in place of derived types
Please visit the link to see a working example.
Following are the links that can be helpful in understanding the topic better.
Link1:
Link2:
Link3:
Hope this was Helpful.
Till next time we connect…Happy Coding.
good one. Explore
ReplyDelete