Skip to main content

Implicit type in C#

C# 3.0 introduced implicit type declaration var. This is not same as var type in JavaScript which is a weak type. The variable is still strongly type however the type is inferred by the compiler based on the value.

E.g. var s = "Joe"; will result in s a string type. Similarly var i = 10; will result i as int type.

However there are certain restrictions on declaring var types
1. Implicit local variable must be initialized.
e.g. var j; will result in error

2. Implicit typed local variable cannot  have multiple declarators
e.g. var i, j=0; is not allowed

3. Cannot assign null to an implicit typed local variable
e.g var i = null; is not allowed

4. Cannot impicitly convert string to int
e.g. var i = "43";
int j = i+ 1; will result in error;

You can use implicit type to create Anonymous types

e.g var person = new {Name="Joe",Age=37};
Console.WriteLine("{0} : {1}",person.Name, person.Age);

Compiler will create class with Read only properties and derives the class from System.Object. You cannot use Anonymous types as return value or parameters. You can use it only as local variables inside a function.

Comments

Popular posts from this blog

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together;  The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0