Skip to main content

Covarianta si contravarianta in .NET 4.0

Covarianta si contravarinata au existat de la .NET 1.0. Schimbarea pe care a adus-o .NET 4.0 a fost ca a introdus aceste funcționalități si in tipurile generice.
In teorie, un tip T este mai mare decat S, daca si numai daca S este un subtip( derivat) din T.
Din acest enunt putem sa ajungem la concluzia ca exista o oarecare unitate de masura prin care se pot descrie tipurile( in forma unui arbore). Putem sa consideram ca T este clasa de baza, iar S este clasa derivata.
Covarianta: daca Generic este mai mare sau egal decat Generic. Covarianta se folosește in special cand vrem ca de la ceva generic sa ajungem la ceva mai particular.
Covarianta ne permite sa tratam un obiect ca si cum ar fi mai sus in ierarhie. Din aceasta cauza se ajunge ca proprietățile sa fie read-only din tipul generic.
De exemplu daca avem un tip de baza Animal si doua clase care moștenesc aceasta clasa( Caine, Sarpe), in mod normal nu am putea sa avem:
public class Animal{}
public class Caine:Animal{}
public class Sarpe:Animal{}

public interface IBox<TAnimal>
{
TAnimal Obiect { get; }
}
...
IBox<Caine> caineBox = null;
IBox<Animal> animalBox = caineBox;
Pentru a putea face acest lucru avem nevoie de:
public interface IBox
{
TAnimal Obiect { get; }
}
Trebue sa tinem cont ca covarianta nu ne permite sa avem:

  • setter pe proprietatea Obiect;
  • o metoda care sa aibe ca parametru de intrare un parametru de tip TAnimal;
  • o metoda care sa aibe ca parametru de intrare un parametru de tip referinta(ref) de tip TAnimal;
Putem sa avem in schimb o metoda ce returneaza tipul TAnimal.
interface IBox
{
TAnimal GetAnimal(); // permis
void Proceseaza(TAnimal value); // nu este permis
void Schimba(ref TAnimal reference); // nu este permis

TAnimal Obiect
{
get; // permis
set; // nu este permis
}
}
Contravarianta: daca Generic este mai mic sau egal decat Generic. Contravarianta se folosește cand vrem ca de la un tip particular sa ajungem la un tip generic. Prin acest mecanism putem sa setam valori in clasa generica.
Contravarianta apare in momentul in care vrem sa avem ceva de genul:
public interface IBox
{
void Adauga(TAnimal animal);
}
...
IBox animalBox = Init();
animalBox.Adauga(new Sarpe());
Operatiile care nu sunt permise pentru contravarianta sunt:
  • o metoda nu poate returna un obiect de tip TAnimal;
  • o metoda nu poate sa accepte ca parametru de intrare un parametru de tip referinta(ref);
interface IBox
{
TAnimal GetAnimal(); // nu este permis
void Proceseaza(TAnimal value); // permis
void Schimba(ref TAnimal reference); // nu este permis

TAnimal Obiect
{
get; // nu este permis
set; // este permis
}
}
Este bine de stiut faptul ca contravarianta poate fi folosita cand este nevoie de nevoie de trecerea de la ceva mai particular la ceva mai generic. Covarianta este asemanatoare cu READ ONLY iar contravarianta cu WRITE ONLY.
Pentru mai multe informatii: http://community.devexpress.com/blogs/paulk/archive/2010/06/18/covariance-and-contravariance-in-net-4-0.aspx
O prezentare foarte interesanta: http://blog.mbharrington.org/2011/02/21/covariance-and-contravariance-in-net-4/

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...