Boxing and Unboxing
Most of us have the knowledge about "Boxing" and "Unboxing".
For "Boxing" means convert value type to reference type.
For "Unboxing" means convert reference type to value.
More deeper,
1. For Boxing, CLR did three things in briefly,
(1) Allocate a heap memory.
(2) Copy the value to heap.
(3) Return the pointer of that "Boxed" type.
2. For Unboxing,
(1) Unboxing.
(2) Copy.
Note that, I mentioned that Unboxing and Copy, because,
(1) For Unboxing, it means that get each filed that contained the boxed type. This process is called unboxing.
(2) For Copy, it means copy the value to the value type instance in the stack.
Why boxing and unboxing?
Consider ArrayList. You may want to add values to the list. But after you dig into the argument of Add method of ArrayList, you found that the parameter is "Object". So, in this case, a boxing is needed. Also, while you are reading the data, you need to convert it to value type, so a unboxing needed.
The disadvantage is, it will impact the performance of your application.
Generic
One much better way is that us "Generic Type". It has below advantages,
1. Type examine while your compiling.
2. Force to value type if you passed the value type.
3. Stack allocated while running.
4. Less operations in heap memory.
5. Less force convertion happened.
How many boxing are there?
Now, let's try to see an interesting code, to see how many boxing are there?
static void Main(string[] args)
{
Int32 i = 5;
object o = i;
i = 123;
Console.WriteLine(i + "--" + (Int32)o);
}
A HA. One? Two? Or Three?
The answer is "three", there are three boxings happened.
Why it's three other 1 or 2?
Before we try to find the root cause, let's understand a keyword in IL called "box", which did the "Boxing". So, if you examine your IL code, you will absolutely found the box keyword. See below IL picture,
So, after you counted the box, you will see "3". And you will also notice that there is a Concat method?
Why there is a "Concat" method?
Please guess it by yourself.
Thanks.