Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
doc: clarify async iterator leak #28997
4 times, most recently
Aug 6, 2019
mcollina left a comment
I don't think we should land this change.
When a stream is async iterated it will always exit the iteration in a destroyed state, i.e.
What should be documented is that, because it's left in a destroyed state, there will be a
The semantics of that are currently not what somebody is going to expect. The two iterators are going to compete for the chunks (as they use
Hence, should we throw if a secondary iterator is created? Also possibly add a note in the docs?