javascript - Why does the logical or operator (||) with an empty arrow function (()=>{}) cause a SyntaxError? - Stack Ove

admin管理员组

文章数量:1341406

In my code, I have something that boils down to this:

var x = y || ()=>{};

(In case you are wondering, I am later calling x() and y may be defined as a function or it might not, so I don't want a TypeError to be thrown if it is not.)

For some reason, this causes a

SyntaxError: Unexpected token )

Why? I found out that

var x = y || (()=>{});

works just fine, but

y || ()=>{}

dosen't work. Is this specced, or a bug in V8 or Chrome? (I tested this only in the latest release of Chrome stable.)

In my code, I have something that boils down to this:

var x = y || ()=>{};

(In case you are wondering, I am later calling x() and y may be defined as a function or it might not, so I don't want a TypeError to be thrown if it is not.)

For some reason, this causes a

SyntaxError: Unexpected token )

Why? I found out that

var x = y || (()=>{});

works just fine, but

y || ()=>{}

dosen't work. Is this specced, or a bug in V8 or Chrome? (I tested this only in the latest release of Chrome stable.)

• javascript
• arrow-functions

Share Improve this question Follow asked Mar 8, 2017 at 18:25 user7586097user7586097 2

• 1 This is described on MDN. It's just the order of parsing. – Scott Sauyet Commented Mar 8, 2017 at 18:32
• 1 Interestingly, this works with a regular function. – user6560716 Commented Mar 8, 2017 at 19:06

Add a ment  | 

3 Answers 3

Sorted by: Reset to default 18

This is normal. Unlike a function expression, which is a PrimaryExpression like other literals and identifiers, and arrow function specifically is an AssignmentExpression and can only appear inside grouping, ma, assignment, conditional (ternary) and yield expressions. Any other operator than those would lead to ambiguities.

For example, if you expect y || ()=>z to work, then also ()=>z || y should be expected to work (assuming symmetric precedence). That however clearly collides with our expectation that we can use any operators inside concise bodies of arrow functions. Therefore, it's a syntax error and requires explicit grouping to work and stay maintainable.

This is not a bug in the JavaScript engine. This behavior is documented.

Although the arrow in an arrow function is not an operator, arrow functions have special parsing rules that interact differently with operator precedence pared to regular functions.

_{Source: https://developer.mozilla/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions#Parsing_order}

try this var x =( y || (()=>{}));

本文标签：