« Bugzilla Issues Index
#3991 — getting an ambiguous export on a module namespace exotic object should return undefined
- bug_id:
3991
- creation_ts:
2015-02-17 17:10:00 -0800
- short_desc:
getting an ambiguous export on a module namespace exotic object should return undefined
- delta_ts:
2015-03-16 14:20:20 -0700
- product:
Draft for 6th Edition
- component:
Modules
- version:
Rev 33: February 12, 2015 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
Dave Herman
- assigned_to:
Allen Wirfs-Brock
- cc:
["dherman", "jorendorff", "samth"]
- commentid:
12850
- comment_count:
0
- who:
Dave Herman
- bug_when:
2015-02-17 17:10:49 -0800
In 9.4.6.8., step 7.b., don't throw a ReferenceError but return undefined.
- commentid:
12852
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-02-17 17:29:21 -0800
actually, it should never get either null or ambiguous back from ResolveReport call because the name has already been checked (steps 3&4) gainst the known export names. those names were determined by GetModuleNamespace and checked using ResolveExport
what I've have there now is an assertion that the resolve bindeing should never be null or "unambiguous".
Can you think of a situation with a binding would dynamically go away? If so, that would seem to be a violation of the requirement that ResolveExport is idempotent and side-effect free.