« Bugzilla Issues Index
#3411 — 15.2.1.1 Early Errors: Incorrect restriction for ExportedBindings
- bug_id:
3411
- creation_ts:
2014-12-07 12:16:00 -0800
- short_desc:
15.2.1.1 Early Errors: Incorrect restriction for ExportedBindings
- delta_ts:
2014-12-23 20:23:26 -0800
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 28: October 14, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
André Bargull
- assigned_to:
Allen Wirfs-Brock
- commentid:
10819
- comment_count:
0
- who:
André Bargull
- bug_when:
2014-12-07 12:16:33 -0800
15.2.1.1 Static Semantics: Early Errors
> It is a Syntax Error if any element of the ExportedBindings of ModuleItemList
> do not also occurs in either the VarDeclaredNames of ModuleItemList, the
> LexicallyDeclaredNames of ModuleItemList, or the ImportedBindings of ModuleItemList.
The restriction does not seem to be correct for:
---
export {a as b} from "mod.js";
---
- commentid:
11125
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-12-20 10:30:45 -0800
fixed in rev30 editor's draft
the ImportedBindings check is unnecessary in this rule and actually ImportedBindings is unnecessary because local bindings created by imports are included in LexicallyDeclaratedNames.
export {a as b} from "mod.js" doesn't actually create any local bindings.
- commentid:
11156
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2014-12-23 20:23:26 -0800
fixed in rev30