# \`AsyncStream\` constructor which also returns its Continuation

**URL:** <https://forums.swift.org/t/asyncstream-constructor-which-also-returns-its-continuation/53251>\
**Category:** Pitches\
**Created:** [November 2, 2021, 8:21pm UTC](https://forums.swift.org/t/asyncstream-constructor-which-also-returns-its-continuation/53251 "2021-11-02T20:21:12Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![jmjauer](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jmjauer/32/15911_2.png) [@jmjauer](https://forums.swift.org/u/jmjauer)\
**Post date:** [November 8, 2021, 8:48pm UTC](https://forums.swift.org/t/asyncstream-constructor-which-also-returns-its-continuation/53251/10 "2021-11-08T20:48:58Z")

</div>

> [@Philippe\_Hausler](#):
>
> I could continue with other ideas but perhaps it might be best to start another thread than hijack this one so we can keep the community thoughts organized.

I agree, this is a huge topic. But I really think it is important to name the elephant in the room in the new thread: [Should AsyncSequence replace Combine in the future, or should they coexist?](https://forums.swift.org/t/should-asyncsequence-replace-combine-in-the-future-or-should-they-coexist/53370)

---

_[View the full topic](https://forums.swift.org/t/asyncstream-constructor-which-also-returns-its-continuation/53251)._
