Skip to content

Implementation Tracking #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
6 tasks done
tchetwin opened this issue Mar 3, 2025 · 3 comments
Open
6 tasks done

Implementation Tracking #47

tchetwin opened this issue Mar 3, 2025 · 3 comments

Comments

@tchetwin
Copy link

tchetwin commented Mar 3, 2025

Things are looking very healthy for when this is ready for Stage advancement:

Implementations

This is considered "Baseline 2024" by MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/fromAsync

@js-choi
Copy link
Collaborator

js-choi commented Mar 3, 2025

Excellent—thank you for collating all of this together.

I plan on progressing this later this year. First we need to address the still-outstanding tasks in #14 (comment). I have had little time to do these, but I hope to push the changes through over the next months.

Once those tasks are done, I will be able to present Array.fromAsync to Stage 4 hopefully later this year.

@js-choi
Copy link
Collaborator

js-choi commented May 1, 2025

Engines will need to update their behavior to close sync iterables when they yield rejected promises (#49).

There is a pending test262 pull request (tc39/test262#4450). This change came from upstream in tc39/ecma262#1849, but it did not affect this proposal’s spec.

When I tested last month, V8 already should pass this test, while Safari 18.4 and Firefox 136.0 did not pass.

I’m not sure whether this tweak should block Stage 4, given that this change stemmed from a change to ecma262 upstream and not specifically this proposal.

I’m also not sure whether there are bugs filed for Safari and Firefox for tc39/ecma262#1849.

@bakkot
Copy link
Contributor

bakkot commented May 1, 2025

The mentioned test262 test has landed, which is usually sufficient to inform browsers about a change.

Safari tech preview should pass as well, since they implemented tc39/ecma262#2600 and their implementation of fromAsync is self-hosted. It takes a while for things to hit stable, is all.

Firefox has not implemented tc39/ecma262#2600 yet, but it's tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1610315 and they'll probably fix fromAsync at the same time.

Anyway, since there are two implementations of the spec'd behavior, this does not affect stage 4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants