Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature request] Implement a new await keyword to deal with configureawait #1320

Closed
MithrilMan opened this issue Jan 6, 2020 · 1 comment
Closed

Comments

@MithrilMan
Copy link

@MithrilMan MithrilMan commented Jan 6, 2020

There is a long time running debate about the fact that ConfigureAwait(false) should have been the default behavior, now I understand it's late to change the default await behavior, but what about introducing a new operator like awaitf (note f char) or a similar concept, that act as a normal await with a ConfigureAwait(false) behavior?
In my example the f char stands for "free" in the sense that it's not capturing context, but my point is not about the real name but about the concept of having an operator that explicitly define the behavior.

This has the pros of having a clear intention while at the same time being backward compatible

what do you think?

@jkotas

This comment has been minimized.

Copy link
Member

@jkotas jkotas commented Jan 6, 2020

You are proposing a new C# language features. https://github.com/dotnet/csharplang repo is the place to discuss new C# language proposals.

Take a look at the similar proposals in csharplang repo:

dotnet/csharplang#645
dotnet/csharplang#2542
dotnet/csharplang#2746

@jkotas jkotas closed this Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.