You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
stream/iter: from() accepts async-only nested values from sync iterables #64351
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
from([asyncGenerator()]) should throw, because the outer source is a sync iterable and the nested value is async-only.
Spec §8.1 says that when from() treats a sync iterator as an async source, nested async iterables and toAsyncStreamable are unsupported. The sync-iterator fallback currently routes nested values through normalizeAsyncValue(), which accepts async iterables and toAsyncStreamable, so the nested async generator is consumed instead of rejected.
Activity
stream: reject nested async streamables in from()
stream: reject nested async streamables in from()
stream: reject nested async streamables in from()
stream: reject nested async streamables in from()