3 ms·
> which on the server goes beyond just providing async await, as lattner said they were aiming at something closer to the actor model I'd be interested in furt
by ngrilly 9y ago
> which on the server goes beyond just providing async await, as lattner said they were aiming at something closer to the actor model
I'd be interested in further information about this, if you can share some link here.
- Someone 9y agohttp://researcher.watson.ibm.com/researcher/files/us-lmandel/lattner.pdf http://researcher.watson.ibm.com/researcher/files/us-lmandel..., page 52: "Async/await are effectively proven at this point and would fit well with the Swift type system and structure, we should probably just do it. Erlang/Akka have proven actor models. Swift providing syntax yields a declarative model which enables programmers to reason about what mutable state goes with each task. Each actor is effectively a DispatchQueue + state it manages + operations that act on it. Actor approach also generalizes well to future. It could be a great way for handling heterogenous compute (e.g. GPU tasks), distributed compute, etc since each async “call” to an actor really is a message send (thus could be DMA or IPC)." I don't think a video of that talk is available online. https://researcher.watson.ibm.com/researcher/view_group_subpage.php?id=6940 https://researcher.watson.ibm.com/researcher/view_group_subp... doesn't mention it.