C# Generics
There is a reality; most of the developers confuse about C# Generics. Actually, there is no reason for that. If your background comes from C++ or Java you may understand more easily. What "Templates" tell you from your C++ knowledge or "Generics" from Java. Main concept is same here in C# with some better extensions and easy usability. For example since C++ Templates uses compile time, C# Generics also a feature of the runtime. They are basically the capacity to have type parameters lying on your type. Generics refer to classes and methods that work homogeneously on values of different types. They are a type of data structure that contains code that remains the same; though, the data type of the parameters can change with each use. We can also call them parameterized types or parametric polymorphism.
The usage of generics within the data structure adjusts to the different data type of the passed variables. Briefly, a generic is a code template that can be applied to use the same code over and over again. Whenever the generic is used, it can be adapted for different data types without require to rewrite any of the internal code.
A List collection class can be a good example:
List Mylist1 = new List();
// No boxing or casting necessary
list1.Add (5);
If we want to expand this code and make it more sensible, we can build something like this:
using System;
using System.Collections;
using System.Text;
namespace TList
{
public class List : CollectionBase
{
public List(){ }
public Template this[int index]
{
get { return (Template)List[index]; }
set { List[index] = value; }
}
public int Add(Template value)
{
return List.Add(value);
}
}
}
If we decide to convert any fields to generic fields, we would just change their types to Template. The generic List doesn't need any fields, but assume a private integer field named test is exist that we would like to make it generic. Here is the sample code:
private Template test;
Generics allow classes, structs, interfaces, delegates, and methods to be parameterized by the types of data they store and manipulate. We can refer to a class, where we don't force it to be related to any specific Type, except we can perform work with it in a Type-Safe approach. We can create a generic collection than can handle any Type in a generic and Type-Safe approach. For example, we can have a single array class to store a list of Employees or yet a list of Items, and as we actually use it, we will be able to access the items in the collection directly as a list of Employees or Items, and not as objects.
Why Generics?
Generics let us to specify our Type at runtime. you can create a collection that is type-safe at compile-time.
Gives no boxing, no casting advantage.
Both the casting and the boxing and unboxing operations degrade performance.
Use of list collection as their new type not as objects.
Binary code reuse
Code clearness with generics is another advantage.
The usage of generics within the data structure adjusts to the different data type of the passed variables. Briefly, a generic is a code template that can be applied to use the same code over and over again. Whenever the generic is used, it can be adapted for different data types without require to rewrite any of the internal code.
A List collection class can be a good example:
List
// No boxing or casting necessary
list1.Add (5);
If we want to expand this code and make it more sensible, we can build something like this:
using System;
using System.Collections;
using System.Text;
namespace TList
{
public class List : CollectionBase
{
public List(){ }
public Template this[int index]
{
get { return (Template)List[index]; }
set { List[index] = value; }
}
public int Add(Template value)
{
return List.Add(value);
}
}
}
If we decide to convert any fields to generic fields, we would just change their types to Template. The generic List doesn't need any fields, but assume a private integer field named test is exist that we would like to make it generic. Here is the sample code:
private Template test;
Generics allow classes, structs, interfaces, delegates, and methods to be parameterized by the types of data they store and manipulate. We can refer to a class, where we don't force it to be related to any specific Type, except we can perform work with it in a Type-Safe approach. We can create a generic collection than can handle any Type in a generic and Type-Safe approach. For example, we can have a single array class to store a list of Employees or yet a list of Items, and as we actually use it, we will be able to access the items in the collection directly as a list of Employees or Items, and not as objects.
Why Generics?
Generics let us to specify our Type at runtime. you can create a collection that is type-safe at compile-time.
Gives no boxing, no casting advantage.
Both the casting and the boxing and unboxing operations degrade performance.
Use of list collection as their new type not as objects.
Binary code reuse
Code clearness with generics is another advantage.
posted by Mayur @ 9:43 PM
0 Comments
