# \[Second review\] SE-0516: \`Iterable\`

**URL:** <https://forums.swift.org/t/second-review-se-0516-iterable/87106>\
**Category:** Proposal Reviews\
**Created:** [June 4, 2026, 3:55pm UTC](https://forums.swift.org/t/second-review-se-0516-iterable/87106 "2026-06-04T15:55:57Z")\
**Posts on this page:** 1\
**Showing post:** 137

<div class="post-metadata">

**Author:** ![broken-circle](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/broken-circle/32/44882_2.png) [@broken-circle](https://forums.swift.org/u/broken-circle)\
**Post date:** [June 24, 2026, 8:38pm UTC](https://forums.swift.org/t/second-review-se-0516-iterable/87106/137 "2026-06-24T20:38:16Z")

</div>

> [@Slava\_Pestov](#):
>
> Perhaps your use case calls for a "Stream" abstraction instead.

@ksluder, this reminded me of the [Generalized asynchronous streaming](https://github.com/apple/swift-async-algorithms/blob/8ee3d2be1961950f94b6fa758477e3a0c5486aa9/Sources/AsyncStreaming/NNNN-async-streaming.md) proposal. It's async-focused and not yet pitched, but you might still find it interesting, along with [this forum thread](https://forums.swift.org/t/lack-of-general-i-o-stream-protocols/87437).

---

_[View the full topic](https://forums.swift.org/t/second-review-se-0516-iterable/87106)._