> On Aug 28, 2017, at 6:56 PM, Howard Lovatt via swift-evolution > <[email protected]> wrote: > > Many of the currently popular server side frameworks are switching to > Reactive Streams: > > http://en.wikipedia.org/wiki/Reactive_Streams#Adoption > <http://en.wikipedia.org/wiki/Reactive_Streams#Adoption> > > for their underlying communication, including Akka. Reactive Streams are also > to become builtin to Java, as the Flow class, in version 9. > > Would it be wise if Swift 5 also builtin Reactive Stream protocols and built > its Actor implementation etc. on top of this protocol?
In MHO, yes, it would be great to build a reactive stream abstraction as well. I agree with you that this is an effectively “obvious” part of the eventual model, and that we will almost certainly end up building it. It would also make sense to have foreach over an async sequence be itself implicitly async. I haven’t sketched that out, but it seems like a few straight-forward steps beyond what is in the manifesto doc. I’ve added a mention of these to the doc, thanks! https://gist.github.com/lattner/31ed37682ef1576b16bca1432ea9f782#further-extensions -Chris > > -- Howard. > > More info on Reactive streams: > > > https://github.com/reactive-streams/reactive-streams-jvm/blob/v1.0.1/README.md#specification > > <https://github.com/reactive-streams/reactive-streams-jvm/blob/v1.0.1/README.md#specification> > > http://bryangilbert.com/post/code/scala/akka-reactive-streams/ > <http://bryangilbert.com/post/code/scala/akka-reactive-streams/> > > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
