archives

« Bugzilla Issues Index

#4168 — Mark parameters of generator methods as optional

• bug_id: 4168
• creation_ts: 2015-03-17 12:01:00 -0700
• short_desc: Mark parameters of generator methods as optional
• delta_ts: 2015-03-17 13:16:03 -0700
• product: Draft for 6th Edition
• component: editorial issue
• version: Rev 35: March 4, 2015 Release Candidate 2
• 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: 13792
• comment_count: 0
• who: Axel Rauschmayer
• bug_when: 2015-03-17 12:01:02 -0700

Sect.: 25.3.1 Properties of Generator Prototype

In several other locations, parameters are marked as optional via square brackets. It may make sense to do that in this section, too.

E.g., how about the following headings?

Generator.prototype.next ( [value] )
Generator.prototype.return ( [value] )
Generator.prototype.throw ( exception )

Long-term, TypeScript’s notation could be adopted (I have done so in my writings and it works well).

---

• commentid: 13794
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2015-03-17 13:16:03 -0700

The signature optional-ness has implications for the length property of the method. In particular, we generally set the length for methods newly defined in ES6 to be the length that would be generated by a corresponding ES function declaration with that signature.

In this case, I don't think we want the length of 'next' and 'return' to not change from 1 to 0.

Changing the spec. signature really has no other implications other than suggesting what is "normal" and in this case I think that all depends upon specific use cases.