Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

What's keeping this from stage 4? #75

Closed
4 of 5 tasks
dead-claudia opened this issue Apr 11, 2019 · 11 comments
Closed
4 of 5 tasks

What's keeping this from stage 4? #75

dead-claudia opened this issue Apr 11, 2019 · 11 comments

Comments

@dead-claudia
Copy link

dead-claudia commented Apr 11, 2019

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:

  • "Test262 acceptance tests have been written for mainline usage scenarios, and merged" - Add coverage for dynamic import test262#1164
  • "Two compatible implementations which pass the acceptance tests" - See next point.
  • "Significant in-the-field experience with shipping implementations, such as that provided by two independent VMs" - Apparently, according to this comment, it's now required even by the HTML spec. If that's not significant enough, I don't know what is. (Also, Node's got an experimental implementation itself.)
  • "A pull request has been sent to tc39/ecma262 with the integrated spec text" - Not filed AFAICT, as I mentioned in my question.
  • "All ECMAScript editors have signed off on the pull request" - See previous point.
@dead-claudia
Copy link
Author

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?

@ljharb
Copy link
Member

ljharb commented Apr 11, 2019

This was discussed at the March meeting; the notes should be available soon.

@aduh95
Copy link

aduh95 commented May 7, 2019

Also, I believe the PR is already opened with the spec text: tc39/ecma262#1482

@dead-claudia
Copy link
Author

@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".)

@ljharb
Copy link
Member

ljharb commented May 8, 2019

That sounds like my recollection; maybe @littledan could update the conclusion in the notes to match theirs?

@littledan
Copy link
Member

littledan commented May 8, 2019

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.

@erights
Copy link

erights commented May 9, 2019

Investigated. Discussed in the SES meeting today. We are happy to see this proceed to stage 4.

@mercmobily
Copy link

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?

@erights
Copy link

erights commented May 11, 2019

I expect it to happen at the upcoming tc39 meeting June 4,5,6 2019

@ctrimm
Copy link
Contributor

ctrimm commented Jun 24, 2019

@domenic or @littledan - I think this can also be closed out since Dynamic Imports is in Stage 4.

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

No branches or pull requests

7 participants