« Bugzilla Issues Index
#3574 — 12.14.5.2 Runtime Semantics: DestructuringAssignmentEvaluation
- bug_id:
3574
- creation_ts:
2015-01-17 17:15:00 -0800
- short_desc:
12.14.5.2 Runtime Semantics: DestructuringAssignmentEvaluation
- delta_ts:
2015-02-02 18:38:57 -0800
- product:
Draft for 6th Edition
- component:
editorial issue
- version:
Rev 31: January 15, 2015 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
minor
- everconfirmed:
true
- reporter:
Axel Rauschmayer
- assigned_to:
Allen Wirfs-Brock
- commentid:
11540
- comment_count:
0
- who:
Axel Rauschmayer
- bug_when:
2015-01-17 17:15:46 -0800
Should `{} = null` throw a TypeError? `[] = null` seems to throw. Similar: `undefined` as rhs.
- commentid:
11543
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-01-18 12:39:08 -0800
Yes, I think you're right.
The reason is that I think both [ ] and { } should be considered assertions that the value that is being assigned to them is coercible to an object (and in the case of [ ], an iterable object)
Also, in 13.2.3.5
fixed in rev32 editor's draft
- commentid:
11993
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2015-02-02 18:38:57 -0800
fixed in rev32 draft