« Bugzilla Issues Index
#1353 — "well-formed rest parameter object"
- bug_id:
1353
- creation_ts:
2013-03-18 22:43:00 -0700
- short_desc:
"well-formed rest parameter object"
- delta_ts:
2014-06-02 12:36:23 -0700
- product:
Draft for 6th Edition
- component:
editorial issue
- version:
Rev 24: April 27, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
Michael Dyck
- assigned_to:
Allen Wirfs-Brock
- commentid:
3499
- comment_count:
0
- who:
Michael Dyck
- bug_when:
2013-03-18 22:43:06 -0700
Some algorithms (15.4.3.3, 15.5.3.2, 15.5.3.3, 15.5.3.4, 15.5.4.6)
assert or assume that something "is a well-formed rest parameter object",
but I don't think this concept is defined.
- commentid:
3758
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-05-12 14:14:41 -0700
Probably need to define at the beginning of Clause 15 what ... means when used in a function signature heading.
- commentid:
8146
- comment_count:
2
- who:
Michael Dyck
- bug_when:
2014-05-04 15:45:03 -0700
The references to "a well-formed rest parameter object" are now in:
21.1.2.1 String.fromCharCode ( ...codeUnits )
21.1.2.2 String.fromCodePoint ( ...codePoints )
21.1.2.4 String.raw ( callSite [ , ...substitutions ] )
21.1.3.4 String.prototype.concat ( ...args )
Also,
22.1.2.3 Array.of ( ...items )
22.2.2.2 %TypedArray%.of ( ...items )
refer to "a well-formed rest argument value", which probably means the same thing.
- commentid:
8480
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2014-05-14 18:55:48 -0700
fixed in rev25 editor's draft
- commentid:
8835
- comment_count:
4
- who:
Michael Dyck
- bug_when:
2014-06-02 12:36:23 -0700
confirmed fixed.