The forked elephant in the room

[ikod]

On Tuesday, 16 January 2024 at 10:13:15 UTC, Richard (Rikki) 
Andrew Cattermole wrote:
>> I'd start from defining event loop API to decouple interface 
>> from implementations.
>
> I have done this in the past. You end up defining the user 
> experience in the process.
>
> Unless you go out of your way with something like coroutines, 
> or fibers, you're pretty much stuck with callbacks of some kind 
> and that is not going to fly.

I had no problems implementing a common API for select, poll, 
epoll, kqueue event loops (never tried Linux io-uring or Windows 
completion ports). This API can be declared and used for 
independent implementations of current and future OS event 
systems.

On top of this implementations for tasks, timeouts, and so on can 
be created.

Are there any reasons why this won't work?