<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div class="">To me, I feel like this would best be implemented as part of Actor model concurrency – taking inputs and emitting outputs is fundamentally what Actors *do*.<br class=""></div></div></blockquote><div><br class=""></div>Yes, I think some form of ‘reactive stream’ could be a prerequisite for the Actor model (an not the other way around).</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">As for naming... I would *not* recommend using `Flow` it is far too generic, has been used in very different contexts and doesn't match terminology in the field.</div></div></blockquote><div><br class=""></div><div>On the contrary, it’s not overloaded at all.</div><div>It is used in <i class="">related</i> concepts like DataFlow, ‘flow-based’ programming, etc.</div><div><br class=""></div><div>Also, from the dictionary:</div><div><br class=""></div><div>flow, <i class="">noun</i></div><div><span style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: small; font-variant-ligatures: normal; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class="">a steady, continuous stream or supply of something.</span></div><div><span style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: small; font-variant-ligatures: normal; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><br class=""></span></div><div><span style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: small; font-variant-ligatures: normal; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class="">sounds like a great synonym for the (reserved?) stream name.</span></div><div><span style="color: rgb(34, 34, 34); font-family: arial, sans-serif; font-size: small; font-variant-ligatures: normal; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);" class=""><br class=""></span></div><blockquote type="cite" class=""><div class=""><div class="">My personal vote is that this topic simply can't be addressed by the standard library at this point. This is something where interoperability with Swift's Actor Model should be a primary concern and until it's done, any action now is only likely to be a headache later.<br class=""></div></div></blockquote><div><br class=""></div><div>I think this is a central concept that among other things is useful in concurrency. It should be tackled sooner rather than later.</div><div><br class=""></div><div>-g.</div><div><br class=""></div></div></body></html>