Click here to Skip to main content

Article

product-showcase

Looking Ahead to C# 7 with Mads Torgersen

Microsoft Canada

17 Mar 2016CPOL

18K

3

6

For the balance of the video Mads Torgersen talks about where C# is headed and some of the thinking behind some new features.

This article is in the Product Showcase section for our sponsors at CodeProject. These articles are intended to provide you with information on products and services that we consider useful and of value to developers.

Mads is a terrific person so we thought we would stop in to bug him about C# 7. For the first 15-20 minutes he mentions some of the C# 6 features you should be already using. For the balance of the video he talks about where C# is headed and some of the thinking behind some new features. Obviously it is early, but in this new era of openness (the compiler has literally been open source'd) it is refreshing to actually get inside the fortress to see strategy. The best part is you can add your voice to the process! Github Repository Enjoy!

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By

Microsoft Canada

Canada

Your Canadian resource for tips, tricks, research, case studies…. Everything you need to develop apps and services that users will love.

This is a Organisation (No members)

Comments and Discussions

ChrisWaldron9-Apr-16 1:41

9-Apr-16 1:41

With the consideration of ref which essentially sounds like a C++ pointer, what about considering deterministic finalization in order to be able to reuse allocation. My issue with the garbage collector is that I have no control when it runs and no control when resources are reclaimed and reused. In tight resource scenarios I have no problem allocating and deallocating so is will there be any consideration of adding deterministism to C#

[My vote of 2] transcript to post

kiquenet.com4-Apr-16 12:30

4-Apr-16 12:30

Audio to written words in a post with main keys about new features C# 6 and 7 ?

Post like What's new in C# 7: The best new features ?

like:

https://www.kenneth-truyers.net/2016/01/20/new-features-in-c-sharp-7

http://www.codeproject.com/Tips/1023426/Whats-New-in-Csharp

What's New in C# 6[^]

IMHO, my suggestions

Video is great indeed.

kiquenet.com

modified 4-Apr-16 18:39pm.

still no type variables

Member 1202398824-Mar-16 3:14

Member 12023988

24-Mar-16 3:14

It's nice that C# 6 dotted some i's and crossed some t's, and there are big features like async/await and pattern matching (which is bound to be done more poorly than in other languages that were designed with it in mind from scratch), but what about major glaring holes in the language, like no type variables (i.e., typedef), which is a huge roadblock to writing good decoupled code and APIs? (using foo = ... is pathetic, especially with its completely pointless limits on where you can put it.)

Re: still no type variables

Mads Torgersen [MSFT]4-Apr-16 12:20

Mads Torgersen [MSFT]

4-Apr-16 12:20

Yeah, I'm not entirely happy with using aliases either. Hopefully one day we'll be able to make it better.

As for pattern matching, we are trying hard to integrate it as deeply as we can with C#. It might not end up as expressive as it is in other languages, but hopefully we can get it to where it is pretty darn useful, and doesn't feel glued on to the language.

Thanks!

Mads

Functional approach to C# and pattern matching

Member 805199418-Mar-16 8:07

18-Mar-16 8:07

This looks good but I would like to avoid having to maintain 2 versions of the same code. One functional and one object oriented. Motivation is that when sending data over the wire, it must be functional approach instead of object oriented. I don't agree, I think you should figure out how to make it work with object oriented approach and not be too influenced by new languages like Go. It means being able to send entire classes with its methods and Properties over the wire with some caching on receiving side(s).

Re: Functional approach to C# and pattern matching

Mads Torgersen [MSFT]4-Apr-16 12:17

Mads Torgersen [MSFT]

4-Apr-16 12:17

Good thoughts, thanks!

While we are inspired by functional languages, it is important for us that we don't create a two-languages-in-one situation. We are trying hard to integrate new features as deeply as we can into existing ones, and keep the "feel of C#" even as we evolve the language.

Stateful object-oriented programming kind of assumes that you have "the one truth" about the object within easy reach. When that's not the case because of a distributed environment, things start to get hard: are you operating on the original or a copy? When and how do they get synchronized? There have been many attempts at solving this, and some of them are successful as they go, but reality is that most people go the simpler route of transmitting information (data), not state (objects). We need to also work well for that.

New features like these mean that sometimes there's more than one way to do things. This means that you have to choose, but hopefully not that you have to do both.

Thanks again,

Mads

General News Suggestion Question Bug Answer Joke Praise Rant Admin

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Go to top