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
Stage 4 tracking #78
Comments
Initial implementation in LibJS has landed: SerenityOS/serenity#16279 (thanks @IdanHo!) |
What exactly can I do as an individual to help this proposal reach stage 4? |
@Nico314159 The thing which is needed at stage 3 is shipping implementations. There's implementations in all the major browsers, but I believe Chrome and Firefox are waiting for test262 tests before they ship. I've written tests at tc39/test262#3966 but they need review from a maintainer. So, nothing individuals can do right now except contribute to maintainership of test262. Contributing test262 tests is often a good way to help stage 3 proposals advance. (Or proposals at the new stage 2.7.) In this case they're already written though. |
Out of curiosity, why is it called stage 2.7? |
It's later than 2, close to 3, but not quite there yet. |
But I why specifically .7? Does it have to do with Euler's number? Or is it just an arbitrary choice? |
Pretty arbitrary i think. |
It was the outcome of an extremely tedious discussion, the dozens of pages of notes for which will be published in a couple of weeks if you need a soporific. |
I genuinely cannot tell if this is a joke or not. |
Alas it is not. TC39 is as susceptible to bikeshedding as any other group. And we do publish transcripts of meetings. We had a little extra time this meeting, which probably contributed to this topic running long. |
Apparently the new set methods arrived in V8 a couple of days ago, so might show up in Chrome soonish? |
Yup, they should be in Chrome 122, which is stable on Feb 14. |
Looks like this has shipped in Chrome and Safari and perhaps will come in Firefox 126, which I imagine will ship around May. |
Implemented in Kiesel, thanks @sno2! |
This proposal achieved stage 3 at the November 2022 meeting. This is a tracking issue for getting stage 4.
The text was updated successfully, but these errors were encountered: