c#-7.0

While investigating the new features in C# 7.x, I created the following class: using System; namespace ValueTuples { public class Person { public string Name { get; } public DateTime BirthDate { get; } public Person(string name, DateTime birthDate) { Name = name; BirthDate = birthDate; } public void Deconstruct(out string name, out int year, out int month, out int day) { name = Name; year = BirthDate.Year; month = BirthDate.Month; day = BirthDate.Day; } public void Deconstruct(out string name, out int year, out int month, out (int DayNumber, DayOfWeek DayOfWeek) day) { name = Name; year =

I want to Map a ValueTuple to a class using reflection. Documentation says that there is a Attribute attached to ValueTuple with parameters names (others than Item1, Item2, etc...) but I can't see any Attribute. Disassembly shows nothing. What's happens? Example: public static T ToStruct<T, T1,T2>(this ValueTuple<T1,T2> tuple) where T : struct Via reflection can't get Item1, Item2 names to match with T fields via reflection. You should have the TupleElementNames attribute on the method created by the compiler. See this code : public class C { public (int a, int b) M() { return (1, 2); } }

Im currently writing an C# application, targeting .NET 4.7 (C# 7). I am confused after I tried using the new way of declaring a variable utilizing the "is" keyword: if (variable is MyClass classInstance) This way it works, but when doing: if (true & variable is MyClass classInstance) { var a = classInstance; } Visual Studio (I'm using 2017) shows me the the Error Use of unassigned local variable 'classInstance' . Using the short-circuting version of & ( && ) it works fine. Am I missing something about the & operator? (I know using the shortcircuting versions are much more commonly used, but at

As we know, C#7 allows to make Main() function asynchronous. What advantages it gives? For what purpose may you use async Main instead of a normal one? David Arno It's actually C# 7.1 that introduces async main. The purpose of it is for situations where you Main method calls one or more async methods directly. Prior to C# 7.1, you had to introduce a degree of ceremony to that main method, such as having to invoke those async methods via SomeAsyncMethiod().GetAwaiter().GetResult() . By being able to mark Main as async simplifies that ceremony, eg: static void Main(string[] args) => MainAsync