frostney / frostney/GocciaScript
Implement Iterator.range
Nobody has claimed this yet.
- Dominant language
- Pascal
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 45
Description
Summary
Implement the Stage 2 TC39 proposal: https://github.com/tc39/proposal-iterator.range
Add lazy Number and BigInt ranges with current endpoints, step/options, inclusive/exclusive, direction, validation, and numeric edge 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
The Iterator constructor and lazy helpers exist, but no standard range iterator does.
Expected behavior
Add lazy Number and BigInt ranges with current endpoints, step/options, inclusive/exclusive, direction, validation, and numeric edge semantics.
Scope notes
Use a dedicated concrete iterator inheriting from %Iterator.prototype%; never materialize or precompute large/infinite ranges. Cover NaN, infinities, signed zero, mixed types, docs, and proposal tests. Additive API: no flag.
Related bytecode roadmap: #871 and #875. Update the relevant language/built-in documentation and Goccia proposal inventory. Use the proposal repository and its current 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 observable 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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing Iterator constructor and lazy helpers, then compare their engine seam and observable behavior with the current TC39 proposal. Define the Number and BigInt range requirements from the proposal before adding focused project tests and pinned Test262 or proposal coverage. Done means proposal behavior, edge cases, documentation, inventory updates, and relevant checks pass without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers, documentation, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100