Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • i guess i was expecting a bit more from C#'s async than it can actually give. I thought that if await exceeds IL instruction or time threshold it switches to the main thread and it will pick up the next async method to execute (in case of my code). Commented May 25, 2019 at 18:22
  • 1
    @alexeyhaidamaka: I would say that's not "expecting more" but "expecting very different" - and I think it would be much worse, by being far less predictable. If an await operator could just get bored and proceed with the next statement, what would you expect it to do if you were using the result of the await operator? It's really important to understand what async/await actually do, because then you can decide on the behavior you want. Commented May 25, 2019 at 18:58