« Bugzilla Issues Index
#3695 — 7.4.6 IteratorClose, 14.4.15 Evaluation yield*: HasProperty + Invoke vs. GetMethod
- bug_id:
3695
- creation_ts:
2015-01-30 16:21:00 -0800
- short_desc:
7.4.6 IteratorClose, 14.4.15 Evaluation yield*: HasProperty + Invoke vs. GetMethod
- delta_ts:
2015-02-02 18:39:06 -0800
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 31: January 15, 2015 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:
11764
- comment_count:
0
- who:
André Bargull
- bug_when:
2015-01-30 16:21:08 -0800
7.4.6 IteratorClose( iterator, completion )
14.4.15 Runtime Semantics: Evaluation
YieldExpression : yield * AssignmentExpression
Using HasProperty + Invoke means two property lookups and it makes it impossible for generator subclasses to opt-out of "return" or "throw". For 22.1.2.1 Array.from it was even decided that two property lookups should be avoided because of possible side-effects in the first property lookup.
Too late to change to use GetMethod instead of HasProperty + Invoke?
- commentid:
11882
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-02-02 11:32:21 -0800
fixed in rev32 editor's draft
- commentid:
12050
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2015-02-02 18:39:06 -0800
fixed in rev32 draft