« Bugzilla Issues Index
#2654 — Is a [no LineTerminator here] needed in the arrow grammar?
- bug_id:
2654
- creation_ts:
2014-04-14 10:05:00 -0700
- short_desc:
Is a [no LineTerminator here] needed in the arrow grammar?
- delta_ts:
2014-04-29 22:45:04 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 23: April 5, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
Luke Hoban
- assigned_to:
Allen Wirfs-Brock
- commentid:
7720
- comment_count:
0
- who:
Luke Hoban
- bug_when:
2014-04-14 10:05:27 -0700
We decided at the last meeting that for the async feature, we want to maintain forward compatibility with the option to elide "()" in arrows fucntions.
As noted in https://github.com/lukehoban/ecmascript-asyncawait/issues/13#issuecomment-40126866 we would have to add an additinal [no LineTerminator here] to the ES6 arrow grammar to ensure we have this option.
<quote>
If we're really trying to preserve the option of elided arrow params, do we want to add that second [no LineTerminator here] restriction to regular arrow functions in ES6? (I don't see that restriction in the current draft.)
// Successfully parses with ES6 grammar
x = y
=> 1;
</quote>
- commentid:
7753
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-04-16 14:50:44 -0700
fixed in rev24 editor's draft
- commentid:
8025
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2014-04-29 22:45:04 -0700
fixed in rev24