« Bugzilla Issues Index
#3257 — Need decision on this binding of ES6 modules
- bug_id:
3257
- creation_ts:
2014-10-05 17:13:00 -0700
- short_desc:
Need decision on this binding of ES6 modules
- delta_ts:
2015-07-10 08:35:01 -0700
- product:
Draft for 6th Edition
- component:
Modules
- version:
Rev 27: August 24, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
blocker
- everconfirmed:
true
- reporter:
Allen Wirfs-Brock
- assigned_to:
Dave Herman
- cc:
["d", "dherman", "erik.arvidsson", "jorendorff", "samth"]
- commentid:
10264
- comment_count:
0
- who:
Allen Wirfs-Brock
- bug_when:
2014-10-05 17:13:25 -0700
I need a final decision ASAP on the this binding visible at the top level of ES6 modules. It could be:
1) the global object
2) the value undefined (good if you need to defer the decision
3) throws when accessed (better if you need to defer)
3) the namespace object of the current module
4) something else
- commentid:
10265
- comment_count:
1
- who:
Erik Arvidsson
- bug_when:
2014-10-06 08:38:42 -0700
1. The global object
We talked about this in the breakout sessions at MS and the conclusion was that we want this to be the global object, even inside modules.
- commentid:
10660
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2014-11-17 15:50:55 -0800
fixed in rev29 editor's draft
- commentid:
10661
- comment_count:
3
- who:
Erik Arvidsson
- bug_when:
2014-11-18 10:31:23 -0800
Domenic told me that we wanted undefined. I don't know when that was agreed upon but I support using undefined too since minimizing the use of this to only be used in classes/methods seems like a good goal.
- commentid:
10853
- comment_count:
4
- who:
Allen Wirfs-Brock
- bug_when:
2014-12-07 14:35:01 -0800
fixed in rev29