Skip to main content

Timeline for async+await == sync?

Current License: CC BY-SA 4.0

10 events
when toggle format what by license comment
Aug 6, 2021 at 7:47 review Suggested edits
Aug 7, 2021 at 10:19
Jul 30, 2020 at 10:03 comment added Seabizkit @Caleth this was posted in 2016, i have a much much better understanding now. reading stuff like this now, in retrospect is difficult as i don't know what i did and didn't know then... but have it all down like a boss in the +-4 years since ;-)
Jul 30, 2020 at 9:24 comment added Caleth @Seabizkit whatever calls you await + async has the opportunity to do other stuff in the mean time. If you should only be able to click one button at a time, then you need to disable the other button before the first await
S Jul 30, 2020 at 8:31 history suggested Michał Powaga CC BY-SA 4.0
Link updated
Jul 28, 2020 at 18:03 review Suggested edits
S Jul 30, 2020 at 8:31
Nov 5, 2018 at 4:01 comment added Andrew What about Console.WriteLine(await GetStringOverNetwork());? What if you need the output of the asynchronous invocation? Would the program block on first access, even if the thread could potentially continue execution?
Dec 7, 2016 at 9:38 comment added Seabizkit Could you explain in more detail. Are you saying... that without this... you would not be able to interact with the UI... as this would be on the main thread. So does this mean that this only become applicable in a application type program apposed to web where interaction is separate from the web server thread. So in a nut shell this only become important i.e. not sync* when your main thread is the running thread. Wouldn't this create unexpected behavior, i.e. in a App(1 main thread) two buttons clicked.. but you should be able to click the 1 without the first completing?
Jan 14, 2013 at 19:13 vote accept Mrchief
Jan 14, 2013 at 19:13 comment added Mrchief Very nicely said!
Jan 14, 2013 at 16:43 history answered Akim CC BY-SA 3.0