Skip to main content

Things I learned at NDC London: The Future of C#

After the first 2 days of workshops, NDC London continued with lots of great speakers and sessions. I was planning to share some information during the conference itself but due to technical difficulties I had to postpone it. For the next few days I will be sharing some of the great content.
One of the sessions that got a lot of traction, was ‘The Future of C#’ session by Mads Torgersen.
Here is a list of some of the language features the C# team is considering:
  • Primary constructors - public class Point(int x, int y) { }
  • Read-only support for auto implemented properties - public int X { get; }=x;
  • Using statement support for static types - using System.Math; Sqrt(X);
  • Support for Property Expressions - public double Distance => Sqrt(X * X + Y * Y);
  • Improved null checking - if (points?.FirstOrDefault()?.X ?? -1) { }
  • Support for Method Expressions - public Point Move(int dx, int dy) => new Point(X + dx, Y + dy);
  • Inline declarations for out parameters - public void Foo(out var x, out var y) { }
  • Support for using enumerables in combination with the params keyword - public Point Average(params IEnumerable<Point> points) { }
I probably missed some features. So if you were there, feel free to share your info. I’ll add the items to the list…

Update: After creating this post, I noticed the following blog post that contains the same info+ some extra details: http://damieng.com/blog/2013/12/09/probable-c-6-0-features-illustrated

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...