frostney / frostney/GocciaScript

Implement Iterator.prototype.chunks and Iterator.prototype.windows

Open
#1,020 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

engine new feature spec compliance
Dominant language
Pascal
Stars
20
Forks
3
Avg merge
3d 4h
Merged PRs (30d)
45

Description

Summary

Implement the Stage 3 TC39 proposal: https://github.com/tc39/proposal-iterator-chunking

Add both lazy helpers with current size/options validation, partial-chunk, overlapping-window, exhaustion, return, and abrupt-completion semantics.

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

Lazy Iterator Helper infrastructure exists, but chunks and windows are absent.

Expected behavior

Add both lazy helpers with current size/options validation, partial-chunk, overlapping-window, exhaustion, return, and abrupt-completion semantics.

Scope notes

Reuse Iterator.Lazy and established re-entrancy/GC patterns; infinite inputs must stay lazy. Add proposal tests, docs, and inventory. Additive API: no feature 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

  • Parser/API surface, descriptors, evaluation order, errors, and protocol behavior match the current proposal.
  • Implementation uses the identified shared engine seam without a duplicate compatibility shim.
  • Focused positive, negative, abrupt-completion, and edge-case tests cover the proposal.
  • Relevant project suites, pinned Test262 cases, formatting, and documentation checks pass.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing Iterator.Lazy infrastructure and the current TC39 iterator-chunking proposal. Trace the shared engine seam and established re-entrancy/GC patterns, then use focused project tests and pinned Test262/proposal cases to cover validation, laziness, protocol completion, and edge cases. Done means both helpers, documentation, and the Goccia proposal inventory are updated and relevant suites and checks pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.