Open Bug 1044462 Opened 10 years ago Updated 2 years ago

Reflect.parse: Support newest export syntax

Categories

(Core :: JavaScript Engine, defect)

defect

Tracking

()

People

(Reporter: me, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release) Build ID: 20140721004001 Steps to reproduce: As per http://people.mozilla.org/~jorendorff/es6-draft.html#sec-exports, `export default (AssignmentExpression)` should be supported as export declaration. Also, parsing `export *` should produce an error when it's not followed by `from "..."` clause. Actual results: Currently, neither is supported in Reflect.parse and Esprima. Expected results: For `export default (AssignmentExpression)`, I propose to use AST from early Esprima version that is used in https://github.com/square/es6-module-transpiler and landed in same representation in Acorn: { type: "ExportDeclaration", declaration: ...(assignment expression)..., default: true, specifiers: null, source: null }
OS: Windows 8.1 → All
Hardware: x86_64 → All
That representation seems fine to me right now, but i'm not looking at the spec (no time at the moment).
Blocks: es6
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 1173387
No longer blocks: es6
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.