Timeline for Trying to understand some async/await behavior
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2016 at 11:01 | history | tweeted | twitter.com/StackProgrammer/status/719118149313028096 | ||
| Apr 5, 2016 at 1:25 | vote | accept | Brandon | ||
| Apr 5, 2016 at 1:25 | history | edited | Brandon | CC BY-SA 3.0 | added 450 characters in body |
| Apr 5, 2016 at 1:22 | answer | added | Karl Bielefeldt | timeline score: 8 | |
| Apr 5, 2016 at 1:22 | comment | added | JimmyJames | Thanks. Very interesting. I await the answer with bated breath. | |
| Apr 5, 2016 at 1:15 | comment | added | Brandon | He's talking about the "await [function]" vs defining the function in a Task<string> variable then calling "await [variable]". Which produces the behavior I described as expected. | |
| Apr 5, 2016 at 1:14 | comment | added | JimmyJames | Would it be too much to ask that someone point out which line(s) you are talking about? | |
| Apr 5, 2016 at 1:11 | comment | added | Brandon | Indeed you are correct. But why does that simple difference cause them to process in order? I have seen in mentioned that essentially when calling an await the following code is processed as a continuation, which would make sense and explain this to some extent. I don't know if that is correct or not, but even the code from the article calls them as consecutive calls which seems to invalidate that statement. | |
| Apr 5, 2016 at 0:42 | review | First posts | |||
| Apr 5, 2016 at 1:43 | |||||
| Apr 5, 2016 at 0:41 | history | asked | Brandon | CC BY-SA 3.0 |