[swift-evolution] Active Objects | Actors | Synchronisations
clattner at apple.com
Wed Jan 13 23:54:43 CST 2016
> On Jan 13, 2016, at 7:24 PM, Suminda Dharmasena via swift-evolution <swift-evolution at swift.org> wrote:
> Unlike in Java a better model for synchronisation would be active objects where you can specify groupings of parallelism or serialism, i.e., being able to specify that calls to a group of functions can only happen one after the other.
> Perhaps this can be in the form of an attribute. E.g. @active(group="ObjXYZStateChange") or @actor(receive="aFunc”)
Many people are interested in synchronization and concurrency designs of many forms, but we can’t handle a full discussion about it in the Swift 3 cycle:
More information about the swift-evolution