Skip to content
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

Reviews for Stage 2.7 #26

Open
1 of 5 tasks
guybedford opened this issue Nov 14, 2024 · 3 comments
Open
1 of 5 tasks

Reviews for Stage 2.7 #26

guybedford opened this issue Nov 14, 2024 · 3 comments

Comments

@guybedford
Copy link
Collaborator

guybedford commented Nov 14, 2024

Issue to track Stage 2 reviewers feedback.

Spec: https://tc39.es/proposal-esm-phase-imports/

Reviewers:

Editors:

@ljharb
Copy link
Member

ljharb commented Nov 14, 2024

to clarify, reviewers are within stage 2, they're just a prerequisite for stage 2.7.

@guybedford guybedford changed the title Stage 2.7 Reviews Reviews for Stage 2.7 Nov 14, 2024
@michaelficarra
Copy link
Member

  1. EvaluateImportCall step 9.b.i: don't say "is not equal to", just say "is not"; see https://github.com/tc39/ecma262/wiki/Editorial-Conventions#comparisons.
  2. GetModuleSourceModuleRecord: wouldn't it be more appropriate to name this parameter specifier? Isn't it still conceptually a specifier?
  3. GetModuleSourceModuleRecord step 5: "is equal to" -> "is"
  4. Source Text Module Records [[SourceText]] field: "ECMAScript source text" is probably a better type. Also I wouldn't include the optimisation note for hosts.
  5. Source Text Module Records [[ModuleSource]] field: like the above rows, we should describe when it's expected to be empty
  6. ModuleSourcesEqual step 2: "is equal to" -> "is"
  7. The ModuleSource constructor: I don't think this is needed: "will throw an error when invoked, where support for dynamic construction may be added in future"
  8. Where is ModuleSourcesEqual called? Why is it on abstract module records and not just source text module records (or better yet, just an AO) if we know it'll only be called on them?
  9. "For Module Records that implement a normal completion" -> "For Module Records that return a normal completion"
  10. I don't love the not-a-source enum name, but we can bikeshed that during integration

@guybedford guybedford mentioned this issue Nov 22, 2024
8 tasks
@michaelficarra
Copy link
Member

LGTM

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