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

Add ES2022 normative change #269

Merged
merged 5 commits into from Jan 3, 2022

Conversation

sosukesuzuki
Copy link
Contributor

@sosukesuzuki sosukesuzuki commented Dec 25, 2021

tc39/ecma262#2154 has been merged to ECMAScript. It will be included in ES2022.

So we should add it to estree spec.

Fixes #270

@sosukesuzuki sosukesuzuki changed the title Add for ES2022 normative change Add ES2022 normative change Dec 25, 2021
es2022.md Outdated
@@ -83,6 +83,33 @@ extend interface BinaryExpression <: Expression {
- `left` can be a private identifier (e.g. `#foo`) when `operator` is `"in"`.
- See [Ergonomic brand checks for Private Fields][proposal-private-fields-in-in] for details.

# Modules

See https://github.com/tc39/ecma262/pull/2154 for more details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: Consider provide a text link instead of url, for example, [Arbitrary module namespace identifier names].

extend interface ImportSpecifier <: ModuleSpecifier {
imported: Identifier | Literal;
}
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider add a note for further restrictions:

If imported is a Literal, imported.value must be a string without lone surrogate.


If `imported` is a `Literal`, `imported.value` must be a string without lone surrogate.

## Exports

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should ExportAllDeclaration also be extended?

export * as "foo" from "mod"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! a22ea89

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

Successfully merging this pull request may close these issues.

import / export should also allow string literals
5 participants