.NET Zone is brought to you in partnership with:

I am a Software Engineer working with the latest in .NET focusing on Web Development. With a burning heart for programming, I blog and author a book about C#. Filip is a DZone MVB and is not an employee of DZone and has posted 54 posts at DZone. You can read more from them at their website. View Full User Profile

Microsoft Open Sources C# Compiler

04.06.2014
| 4792 views |
  • submit to reddit

VS2013LogoThis is truly an extremely exciting time, Microsoft is Open Sourcing the C# Compiler (Roslyn). Even without being open source, the new C# (and VB) compiler have had some proven potential. We have seen some exciting things such as semantic merge and powerful plugins for Visual Studio.

Now that the source is out there and they are accepting contributions – where do you think this will end? Personally, I cannot even imagine what the community will come up with.

C# Compiler Source Code Available Here.

C# 6.0

During the last year, we have seen some announcements on coming features in the next version of C#, with the compiler being open source there is a roadmap and list of features coming in each language.

I thought I would share a bunch of them that excites me the most!

Primary constructors

Instead of having to create your primary constructor yourself and initialize your fields manually, you can now take advantage of Primary constructors, which will turn up in the class declaration and look like this:

public class Point(int x, int y) 
{ 
}
Auto-property initializers and Getter-only auto-properties

Now that we have the primary constructor we want to be able to initialize our properties with these values, instead of creating the constructor the old fashion way, we can do it a bit more nicely with the initializers:

public class Point(int x, int y) 
{ 
    public int X { get; set; } = x;
    public int Y { get; } = y;
}
Using static members

Imagine how often you do Console.WriteLine in a console application. Would it not be nice if you could just define somewhere that you want to include the static members and have the accessible directly in your class?

You can do that now by simply adding a using statement for the static type!

using System.Console;

public class Point(int x, int y) 
{ 
    public int X { get; set; } = x;
    public int Y { get; } = y;

    public void Print()
    {
         Write(x);
    }
}
Dictionary initializer

Whenever I create a dictionary, I feel it is quite cumbersome to easily initialize it with some temporary values. Now with dictionary initializers that is quite easy!

new JObject { ["x"] = 3, ["y"] = 7 }
Declaration expressions

Whenever you are working with methods that require an out parameter, you always have to create that variable before calling the method, which is a bit ugly so with declaration expressions this is fixed!

int.TryParse(s, out var x);
Binary literals and Digit separators (Planned)

Sometimes working with numbers can be a bit hard, especially if you have long numbers, hex or binary to work with. It might get a bit easier; this is a planned feature for C# as it has already done for VB.

Binary literals will look like this: 0b00000100
Digit separators will look like this: 0xEF_FF_00_A0

Expression-bodied members (Planned)

This is a C# feature only, as of now this is just planned but is not planned at all for VB. Sometime you just want to have an expression that calculates a couple of things for you, but you might not want to be as expressive as creating a method. Expression-bodied members let you do this in a clean and short way.

public double Dist => Sqrt(X * X + Y * Y);
Null propagation (Planned)

How many of you have had a null point reference exception? I would imagine quite a few.

I tend to get them when working with partially loaded data, let us say that I have a Customer that in its turn have a bunch of Orders and the order has a price.

To ensure that we do not get an exception, we would have to check each parameter first before even trying to access price.

With null propagation, you do not have to do that, you simply have a way of expressing yourself in a manner that will evaluate the entire expression to null if one of them is null:

customer?.Orders?[5]?.$price

This means if Orders is null or the Order that we fetched was null, we do not get a null reference exception.

String interpolation

When working with string concatenation and adding values into a string, you normally use a string builder orstring.Format. Personally, most of the times I just want to add a name of a person or information about the person, or something similar. Which makes string.Format come off as chatty.

Instead, we could maybe do something like this:

"\{p.First} \{p.Last} is \{p.Age} years old."

I say maybe because this feature is not even planned for either C# or VB.

These are not all of the language features in the next version of C#, but these are some of my favourite ones.

Which ones are you looking forward the most to?

Examples taken from the Language feature implementation status page on the Codeplex website and the list here might not be complete.

The post Microsoft Open Sources C# Compiler appeared first on Filip Ekberg's blog.

Published at DZone with permission of Filip Ekberg, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)