Skip to content

Clarify what should be in quiver.async vs quiver.streams #177

Closed

Description

quiver.streams was supposed to be a Stream equivalent of quiver.iterables, but it has things with no equivalent and/or that don't work on a Stream or collection of Streams (like how quiver.iterables works on ... Iterables) like collect and StreamBuffer. It's possible we want to move those to quiver.async.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions