« Bugzilla Issues Index
#3573 — 12.14.5.2 Runtime Semantics: DestructuringAssignmentEvaluation
- bug_id:
3573
- creation_ts:
2015-01-17 16:55:00 -0800
- short_desc:
12.14.5.2 Runtime Semantics: DestructuringAssignmentEvaluation
- delta_ts:
2015-01-20 10:46:29 -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:
WONTFIX
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
Axel Rauschmayer
- assigned_to:
Allen Wirfs-Brock
- commentid:
11538
- comment_count:
0
- who:
Axel Rauschmayer
- bug_when:
2015-01-17 16:55:10 -0800
It feels like the following case can be handled via KeyedDestructuringAssignmentEvaluation (like the case after it).
AssignmentProperty : IdentifierReference Initializer_opt
- commentid:
11544
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2015-01-18 13:10:31 -0800
That doesn't quite work because of how the grammar productions are factored. Basically, the Initializer is at different levels in the two parse tress.
The body of the KeyedDestructuringAssignmentEvaluation rule could probably be factored out into an abstract operation that was used for both cases. But it seems late in the process to be making that big of a refactoring unless it is also needed to fix an actual semantic bug.
- commentid:
11552
- comment_count:
2
- who:
Axel Rauschmayer
- bug_when:
2015-01-19 12:57:43 -0800
Yes. Not worth the risk.