>... it makes possible fully deterministic, ultra high performance,extensible, composable, asynchronous standard i/o. That’s huge. No other contemporary systems programming language would have that: not Rust, not Go, not even Erlang. Holy shit.
-
-
- Kraj razgovora
Novi razgovor -
-
-
Very interesting, I'm glad we could get rid of unnecessary allocations! Very interested in seeing this used with io_uring, and see the differences with IOCPhttps://hub.packtpub.com/linux-5-1-out-with-io_uring-io-interface-persistent-memory-new-patching-improvements-and-more-2/ …
-
The libunifex project by
@lewissbaker demonstrates using sender/receiver with io_uring.https://github.com/facebookexperimental/libunifex …
Kraj razgovora
Novi razgovor -
-
-
This is utterly incredible. I have suspended the input clause for the graphics paper and await (yo ho!) the outcome (stop, you're killing me!) of the discussion of this proposal. Outstanding work Niall!
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I like this direction. Fyi, we have a library that wraps windows socket, pipe, sharedmem circular buffer and provide inter-process communication using rxcpp observables on top of them.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
> I appreciate that for those who have only ever used ASIO in its default out of the box configuration, it is hard to imagine an asynchronous i/o API which doesn’t have an i/o service dispatching i/o completions to whichever next kernel thread becomes idle.pic.twitter.com/PoEf0y2gIB
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.