libunifex
libunifex copied to clipboard
facebookexperimental
Unified Executors
We would ideally like to be able to define coroutine tasks that can pass through context from the caller to child coroutines to allow passing things like stop_token, current scheduler,...
Implement some of the low-latency ideas from llfio's experiments with sender/receiver that allow I/O operations to complete prior to the completion event being posted to the IOCP queue by polling...
Right now libunifex includes `io_uring.h` in a public interface header file, and requires cmake targets consuming libunifex to include liburing. liburing is not a commonly installed library, plus it is...
The schedulers for these two execution contexts do not yet satisfy the 'time_scheduler' concept because they don't implement the `schedule_after()` CPO, only the `schedule_at()` and `now()` CPOs. We should add...
The current implementation of `range_stream` produces a stream of integers in some specified range. This was largely built just so we had some kind of stream that we could test...
It would make https://github.com/facebookexperimental/libunifex/blob/master/doc/api_reference.md easier to navigate.
Add a "many sender" concept that can send a sequence of calls to a "many receiver": * zero or more `set_next()` calls followed by; * a call to one of...
One of the design goals is to allow algorithms to be customised when invoked with certain types to allow more efficient implementations of that algorithm to be used. One of...
The code assumes that the contracts will be followed and invokes undefined behavior when they are not. This reduces confidence when landing changes. Introduce wrappers that check contracts and terminate...
