Note that there are some explanatory texts on larger screens.

plurals
  1. USDavid
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. CO@jp2code: I wanted to build a maintainable project where it is easy to understand the cascading occurence of events required for special actions to be taken (see the part with → symbols). I guess I will go for a deterministic automaton to handle that - actually async/await gets transformed into nothing else than a FSM by the compiler. It would have been just awesome to find a way to "reuse" the already implemented mechanism and not to reinvent the wheel. Hope I haven't misunderstood your question.
      singulars
    2. COThe big magic is not "that big magic", as it seems. The compiler takes the code practically as it is (loops get translated to jumps etc.), but every await is replaced with "some GetAwaiter call...then some get_IsCompleted call...then some setting of a state var...then some GetResult call". Some preable is added in order to be able to jump to the different states and some error handling wrapped all around. Seems rather like pattern matching than some challenging control flow analysis+code restructuring. That is what I was expecting. Or is there some heavy computation required which I don't see?
      singulars
    3. COI followed your advice and reported it (see https://connect.microsoft.com/VisualStudio/feedback/details/775990/await-array-by-implementing-extension-method-for-array-does-not-compile). Thanks for your investigation effort.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload