-
### Background and motivation
We got new `ValueTask` types earlier in .Net Core to avoid unnecessary allocations. It covered cases for synchronously-completed tasks and reusable task states. Also w…
-
When an async method yields for the first time, we get several allocations:
- The state machine boxed to the heap
- An Action to be used for continuations
- A “MoveNextRunner” in the infrastructure…
-
Thanks for this fantastic library @Naios. The amount of work you must have put into the documentation is really appreciated.
I'm wondering whether reusable continuation chains are a planned feature…
-
Since there isn't a discussion tab, I'm having to post an issue.
Does anyone have opinions on the use of stackful vs stackless coroutines in asio?
Some of the discussion points?
* Performance
*…
-
I'm writing it as a note to myself and maybe other guys who plan/use CLS (continuation-local-storage).
I met several practical problems with it. But my another issue hangs about half-year+ without an…
-
With the recent modifications removing direct programmer access to the chain continuation primitives (promise, resolve, reject), and the addition of concurrency for the system reducer, the following p…
-
Hitting on rolling builds, and PRs. This is when building the tests with AOT, and happens on linux, and windows.
[Build](https://dev.azure.com/dnceng/public/_build/results?buildId=1641292&view=logs…
-
**NLog version**: 5.3.4
**Platform**: .NET6
**Current NLog config** (xml or C#, if relevant)
```xml
…
-
### Summary
The current implementation of closure iterators sees the implementation use a [duff's device](https://en.wikipedia.org/wiki/Duff%27s_device) to implement the state machine between each `y…
-
The README states:
> node-fibers: This implementation of coroutines is unfortunately limited to Node.js. ES6 generators may be simpler, but fibers are more flexible and support a far broader space of…
gunar updated
6 years ago