The QueueProcessor example could have been written using channels, which expose async APIs. Otherwise, as others have commented, I despise how async/await is "

The QueueProcessor example could have been written using channels, which expose async APIs. Otherwise, as others have commented, I despise how async/await is "95% done". The remaining 5% will come to bite haunt you and the documentation is less than satisfiyng. E.g., how does TaskScheduler interact with async? Nowhere documented, except answered on StackOverflow by Stephen Cleary that "it should work". I prefer Java's CompletableFuture and Executors. It's more verbose, but at least there's no hidden magic. From the documentation you can infer exactly how it'll behave.