


What will be placed in the output parameter if the function fails?

Why can’t you return an IAsyncAction from a coroutine that also does a co_await?

When I ask the GetIpAddrTable function to sort the results, how are they sorted?

If one program blocks shutdown, then all programs block shutdown

The type-dependent type or value that is independent of the type

Creating a non-agile delegate in C++/WinRT, part 4: Waiting synchronously from a background thread

Creating a non-agile delegate in C++/WinRT, part 3: The other cases and why they aren’t interesting

Creating a non-agile delegate in C++/WinRT, part 2: The synchronous coroutine
Old New Thing

It rather involved being on the other side of this airtight hatchway: Planting files onto a custom PATH
Adding a directory to the PATH comes with obligations.

What will be placed in the output parameter if the function fails?
Officially, it could be anything. In practice, though, there are some constraints.

Why can’t you return an IAsyncAction from a coroutine that also does a co_await?
You already returned. No take-backs.

When I ask the GetIpAddrTable function to sort the results, how are they sorted?
Nothing particularly fancy. Just plain numerical order.

If one program blocks shutdown, then all programs block shutdown
We're all in this together, as far as the Blocked Shutdown Resolver is concerned.

The type-dependent type or value that is independent of the type
To delay the evaluation until instantiation.

Creating a non-agile delegate in C++/WinRT, part 4: Waiting synchronously from a background thread
Using things you already have.

Creating a non-agile delegate in C++/WinRT, part 3: The other cases and why they aren’t interesting
We handled only one case, but that's the only one worth handling.

Creating a non-agile delegate in C++/WinRT, part 2: The synchronous coroutine
It awaits without waiting.