Modernize business-critical .NET applications by using containers

Learn about the new features available in C# 7.1 and 7.2, including async Main, default literals, ref extension methods, in parameters and more. Also get a glimpse of the future with nullable reference types.
Product info: www.dot.net
Learn more: docs.microsoft.com/en-us/dotnet/csharp/
Documentation: docs.microsoft.com/en-us/dotnet/csharp/whats-new/
Yeah! C# non-nullable reference types :D
This nullable reference types feature looks great! I'm excited for C# 8 :)
I get the feeling that building existing code in C# 8.x with the nullable reference types may not work that well. There are a lot of default constructors out there with reference members. I can see a lot of ?s being typed before code builds.
Beautiful! C# feels more and more comfortable as it's evolving. Looks like you manage to keep that right balance.
I would prefer "readonly ref" instead of "in" for method parameters.
That would be more readable (immediately obvious) and consistent to the return parameters.
Great!!
Amazingly described
Null reference types look great for new projects, however I'm not so sure how well this will play with existing code.
Thank you so much, I wish all your videos be short and extensive like this, especially Xamarin guys (too much of talk very little of information)
@Gysmo:
I get the feeling that building existing code in C# 8.x with the nullable reference types may not work that well. There are a lot of default constructors out there with reference members. I can see a lot of ?s being typed before code builds.
As mentioned this causes warnings, not errors => you code will build just fine. I do agree however that it's nice if you start with a new project. Even existing projects, even small ones, you probably get 1 billion warnings, making it quite annoying.
The 'in' keyword for struct method parameters sounds really, really nice. Unsure if it should be renamed, but hopefully will throw a compiler error for reference types.
Man, C# is looking better and better every year! I can't wait to see what C# 8.0 is going to bring to the table, especially considering how awesome nullable reference types look. Keep up the good work! 👍
the nullable reference? really? isn't c# at its core having a reference nullable? guys, wtf?
stop bringing so much blink blink to c#, it was a beautiful simple language and it's becoming a monster. what happened with keep it simple and stupid? even with a language like that people will build monstrosities, just imagine what they will do with this latest c# which got so much blink blink!
The Ref's: "We were such idiots that we left pointers out of the language at the beginning.."
I think I would prefer the implementation of nullable reference to be the reverse where the intent is expressed on the nullable variable. With all these changes, code readability is becoming a concern.