On Sun, 2016-03-13 at 20:39 +0300, Dmitry Olshansky via Digitalmars-d wrote: > […] > Yeah, preferably we'd have future+async style concurrency together > with > actor system all riding on top of some core functionality like > thread > pools with work-stealing. IO complicates matters as it also has to be > a > part of the picture for 'fiber as actor' model to work really well.
Rust threw out async+future in favour of thread+channel – in the language core, async+future still there but "demoted" to being a library. -- Russel.=============================================================================Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.ukLondon SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
