Play The future of C#
Sign in to queue


Over the last year we shipped no less than three "point releases" of C# (7.1, 7.2 and 7.3), full of small but useful language features. Mads and Dustin will race you through a tour of these, before turning to some of the big things we have in store for the future: Nullable reference types, recursive patterns, asynchronous streams and more.



Session Type:

Breakout 75 minute




WSCC: Ballrooms 6E



Right click to download this episode

Download captions

The Discussion

  • User profile image


  • User profile image

    Please hurry. I like to watch the video! ;)

  • User profile image

    The tags are messed up. C# isn't even included.

  • User profile image

    where is the 2018 video?

  • User profile image

    We are waiting for the video

  • User profile image

    So, the video is offline, but it is still embedded here anyways for some reason.

  • User profile image

    So what we wanted was parity with what VB's select case is capable of. What we got was sugar over a closure extension method that anyone could have written on their own. Yawn.

  • User profile image

    This kinda presentation was kinda not so nice.
    It was kinda fun though. Maybe the even "funnest":
    - making fun of the JavaScript language, Anders Hejlsberg
    - not being 110% prepared for the speech
    - briefly and idiosyncratically "explaining" what out parameters are, without a prior plan, like a kid having to recite a poem and then move on to the next thing
    - not being aware or hiding the fact that languages die out sooner or later because of their own changes which finally jam them in their tracks and that this is not a joke

  • User profile image

    Is the demo source code available somewhere?

  • User profile image

    Great Show

  • User profile image

    @UnUndoable: Which language died out "because of its own changes"? Languages die out due to lack of development, not because of it. Especially not in the case of C#, whose strongest point is that it's been co-evolving with Visual Studio since its birth. The vast of the features are very convenient to learn and use due to the language having a more fine-tuned IDE integration than pretty much any other language in existence. But even if it didn't, what you said is still factually incorrect.
    Also, it's not set in stone that features cannot be taken away or changed without backward compatibility. Been done before in C#, just usually not the way of the development team deals with things. But when it becomes a serious issue, it does happen.

Add Your 2 Cents