|
| IO tasks are not CPU bound and thus do not require a thread. The main point of async is to not block threads during IO bound tasks. ??? juharr May 24 at 16:55 |
| 19 |
| @jdweng: Nope, not at all. Even if it created new threads, that's very different from creating a new process. ??? Jon Skeet May 24 at 16:57 |
| 6 |
| If you understand callback-based asynchronous programming, then you understand how await/async works without creating any threads. ??? immibis May 24 at 21:18 |
| 3 |
| It doesn't exactly make an application more responsive, but it does discourage you from blocking your threads, which is a common cause of nonresponsive applications. ??? Owen May 24 at 22:18 |
| 2 |
| @RubberDuck: Yes, it may use a thread from
the thread pool for the continuation. But it's not starting a thread in the way that the OP imagines here - it's not like it says "Take this ordinary method, now run it in a separate thread - there, that's async." It's much subtler than that. ??? Jon Skeet May 25 at 5:18 |