Champion "Async Main" (C# 7.1)

[gafter]

• Proposal added: proposals/async-main.md
• Discussed in LDM
• Decision in LDM
• Finalized (done, rejected, inactive)
• Spec'ed

See also dotnet/roslyn#1695 dotnet/roslyn#7476

[yaakov-h]

Can we add a link from the above post to the proposal text?

[stephentoub]

Can we add a link from the above post to the proposal text?

Done

[jcouv]

Some LDM notes:

• https://github.com/dotnet/csharplang/blob/master/meetings/2017/LDM-2017-04-18.md#asynchronous-main

[dbmercer]

Meh. I don't really see much gain from this purely syntactic sugar change. The lack of an async Main may have been an oversight, but this solution doesn't resolve the oversight. Sure, now you can have an async Main, but you gain nothing over what you could have previously done with one line of code. An alternative async Main implementation could have passed in a cancellation token, and had the runtime host cancel the token if, say, a kill signal was received.

[nbarbettini]

Sure, now you can have an async Main, but you gain nothing over what you could have previously done with one line of code.

I think this is still valuable, because it reduces confusion. Having to hit StackOverflow to learn that I need to add .GetAwaiter().GetResult() is nonobvious for a newbie.

An alternative async Main implementation could have passed in a cancellation token, and had the runtime host cancel the token if, say, a kill signal was received.

This would be great. I'd love to see built-in passing of a cancellation token that was linked to the kill signal. 👍