-
Notifications
You must be signed in to change notification settings - Fork 3
Implement Async Iterator Helpers #1023
Copy link
Copy link
Open
Labels
engineTGocciaEngine: language semantics, ECMAScript built-ins, parser, interpreter, bytecode VMTGocciaEngine: language semantics, ECMAScript built-ins, parser, interpreter, bytecode VMnew featureNew feature or requestNew feature or requestspec complianceMismatch against official JavaScript/TypeScript specificationMismatch against official JavaScript/TypeScript specification
Milestone
Description
Metadata
Metadata
Assignees
Labels
engineTGocciaEngine: language semantics, ECMAScript built-ins, parser, interpreter, bytecode VMTGocciaEngine: language semantics, ECMAScript built-ins, parser, interpreter, bytecode VMnew featureNew feature or requestNew feature or requestspec complianceMismatch against official JavaScript/TypeScript specificationMismatch against official JavaScript/TypeScript specification
Summary
Implement the Stage 2 TC39 proposal: https://github.com/tc39/proposal-async-iterator-helpers
Implement AsyncIterator.from plus all lazy and terminal helpers in the current draft with correct sequential awaiting and closing.
Why
This proposal fits GocciaScript's modern ECMAScript surface and the 0.13.0 proposal roadmap. It should extend the engine's existing architecture rather than arrive as a userland shim.
Current behavior
Async generators, Symbol.asyncIterator, for-await-of, and Array.fromAsync exist, but the AsyncIterator intrinsic/helper family is absent.
Expected behavior
Implement AsyncIterator.from plus all lazy and terminal helpers in the current draft with correct sequential awaiting and closing.
Scope notes
Reuse async-generator, Promise job, iterator-close, and GC-rooting infrastructure rather than blocking wrappers around sync helpers. Cover async-from-sync, thenables, re-entrancy, abrupt completion, GC, timeouts, docs, and tests. Additive API: no flag.
Related bytecode roadmap: #871 and #875. Update relevant documentation and the Goccia proposal inventory. Use the current proposal specification at implementation time; add focused project tests and matching pinned Test262/proposal coverage without regressions.
Acceptance criteria