-
Notifications
You must be signed in to change notification settings - Fork 47
What's keeping this from stage 4? #75
Comments
Okay, now that I'm looking through the issues, I see there are some security holes produced by shipping it without realms, but I don't see anything else clearly blocking it. Is my understanding correct in this? |
This was discussed at the March meeting; the notes should be available soon. |
Also, I believe the PR is already opened with the spec text: tc39/ecma262#1482 |
@aduh95 Updated. I have since read the notes, and it seems to partially confirm my theory while noting a few other things. @ljharb The "Conclusion/Resolution" for that section doesn't really make sense. Would you be able to offer any more insight into that? (If I'm interpreting the notes correctly, it's more like "Investigate ramifications with realms and other related proposals, and then consider advancement in June".) |
That sounds like my recollection; maybe @littledan could update the conclusion in the notes to match theirs? |
I plan to propose this for Stage 4 in the June 2019 meeting. The plan was that @erights would spend these two months investigating whether there would be issues with putting Realms on top of this proposal. |
Investigated. Discussed in the SES meeting today. We are happy to see this proceed to stage 4. |
ESLint won't support this till it's stage 4 - even though it's widely used. Since it looks like it's ticking all of the boxes, do you have an estimate of when it will proceed to stage 4 officially? |
I expect it to happen at the upcoming tc39 meeting June 4,5,6 2019 |
@domenic or @littledan - I think this can also be closed out since Dynamic Imports is in Stage 4. |
Given how pervasively this is used and how stable it's become, is there any reason this is still stage 3 apart from opening a tc39/ecma262 PR and putting it to a committee vote? Going through the process document requirements:
The text was updated successfully, but these errors were encountered: