archives

« Bugzilla Issues Index

#2410 — export { yield } should not be allowed

• bug_id: 2410
• creation_ts: 2014-01-01 08:11:00 -0800
• short_desc: export { yield } should not be allowed
• delta_ts: 2014-02-15 17:29:53 -0800
• product: Draft for 6th Edition
• component: technical issue
• version: Rev 21: November 8, 2013 Draft
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: WORKSFORME
• priority: Normal
• bug_severity: enhancement
• everconfirmed: true
• reporter: Jo Liss
• assigned_to: Allen Wirfs-Brock
• cc: andrebargull

---

• commentid: 6959
• comment_count: 0
• attachid: 69
• who: Jo Liss
• bug_when: 2014-01-01 08:11:23 -0800

Created attachment 69
highlighted productions in spec

The ES6 draft seems to allow

export { yield }

and

export { yield as Identifier }

I assume this is an error in the text.

Highlighted resolution path for the ExportDeclaration production is attached.

---

• commentid: 6960
• comment_count: 1
• who: Jo Liss
• bug_when: 2014-01-01 08:33:48 -0800

Wait, is `export { yield }` actually allowed and it just exports the variable named "yield" as a named export?

If so, please close this bug. Sorry for the fuss.

Is there an annotated version of the spec somewhere yet, which would explain these kinds of things?

---

• commentid: 7202
• comment_count: 2
• who: André Bargull
• bug_when: 2014-02-07 04:50:51 -0800

Module code is always strict code (see 10.2.1 Strict Mode Code), so the additional early error restriction in 12.1.2.1 applies which explicitly disallows "yield" as an IdentifierReference in strict code:
---
12.1.2.1 Static Semantics: Early Errors

NonResolvedIdentifier : yield
- It is a Syntax Error if the IdentifierReference is contained in strict code.
---