Support stored Map and Set iterators in static builds - #618
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stored typed Map and Set iterators previously had no static lowering. This change lets
const cursor = map.values(); cursor.next()compile without an embedded engine, and supports passing cursors,for...of, spreads, and mapper-lessArray.from.Reuse native live cursors and preserve reference identity for records, arrays, classes, and supported unions. Keep iterator helper methods such as
.map()and.take()explicitly refused, and update differential fixtures, diagnostic snapshots, documentation, and the generated surface manifest.Validation:
Full-suite validation is incomplete: the sanitized multi-instance library probe reports a 164-byte leak, reproduced on the unchanged starting commit
54d05461b8141731077fe303b697a925bce934d6. The broader plain run was stopped after confirming that existing full-gate blocker.