« Bugzilla Issues Index
#3118 — Reflect.Loader.prototype.set should reject non-module arguments
- bug_id:
3118
- creation_ts:
2014-08-11 14:48:00 -0700
- short_desc:
Reflect.Loader.prototype.set should reject non-module arguments
- delta_ts:
2015-03-16 14:30:23 -0700
- product:
Draft for 6th Edition
- component:
deferred features
- version:
Rev 26: July 18, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
WONTFIX
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
Jason Orendorff
- assigned_to:
Allen Wirfs-Brock
- cc:
["dherman", "jorendorff", "samth"]
- commentid:
9755
- comment_count:
0
- who:
Jason Orendorff
- bug_when:
2014-08-11 14:48:40 -0700
LinkDeclarativeModules assumes that modules in the Loader's [[Modules]] registry are actual Module objects:
- Step 3 makes a List 'resolvedDeps' of Records mapping module names to Module Objects. Items from the Loader's [[Modules]] registry can be stored in this List. The List is stored in pair.[[Module]].[[Dependencies]].
- Step 5 calls ResolveImportEntries and LinkImports, which are meant to use the module's [[Dependencies]] to link it to the other modules it depends on.
Anyway -- as far as I know, because linking requires actual module objects, Reflect.Loader.prototype.set must do a type check and refuse to add non-module objects to the registry.
- commentid:
13753
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-03-16 14:30:23 -0700
concerns old module spec.