With many thanks to @lewissbaker @kirkshoop and @ericniebler
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Execution context should be able to handle remote execution, either with IPC or actual remote invocation through the network. It should be responsible for holding data. For instance, the default executor should hold the global variables, like threads hold their local storage.
-
How do you serialize the receiver?
- Još 2 druga odgovora
Novi razgovor -
-
-
Am I wrong in seeing here similarities with the concept of signals and slots? A slot would be a receiver, a signal would be a sender. Slots can be associated to an "execution context" of sort.
-
I think there are only surface similarities. There is a receiver by sender and it's not broadcasted. A sender is closer to a future. It's a handle to somewhere where work can be done later.
- Još 2 druga odgovora
Novi razgovor -
-
-
awesome, thanks! exactly what I wanted to know for a while, but didn't manage to find time to read the whole executors paper :D
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Thanks a ton for this write up
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Still having a hard time to see why calling something "receiver" that is called "observer" in *any* other PL has any advantage other than drawing people who want to learn C++ crazy. Not that I don’t appreciate reinventors of the wheel, but this is simply unnecessary.
-
Same for “subscribe" renamed to "submit".
- Još 1 odgovor
Novi razgovor -
Č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.