Why we have to wrap throw with brackets in es6 arrow functions

Question

I want to ask if someones knows the reason why

const fun = msg => throw new Error( msg ); is invalid JS while

const fun = msg => { throw new Error( msg ); } is valid

Since

const fun = msg => new Error( t ); is valid

Someone (I would) would expect also the case with throw to be valid JS.

Is there any reason behind this choice? e.g. does it makes it difficult to the interpreter or something?

Because it would be equivalent to `function(msg) { return throw new Error(msg); }` — Bergi, Apr 02 '16 at 18:12

Oriol · Accepted Answer · 2016-04-02T18:01:27.880

Arrow functions are defined like this:

ArrowFunction_{[In, Yield]} :
    ArrowParameters_[?Yield] [no LineTerminator here] => ConciseBody_[?In]

ConciseBody_[In] :
    [lookahead ≠ { ] AssignmentExpression_[?In]
    { FunctionBody }

And throw is an statement:

ThrowStatement_[Yield] :
    throw [no LineTerminator here] Expression_{[In, ?Yield]} ;

Then the first ConciseBody body syntax won't work because AssignmentExpression doesn't include statements:

AssignmentExpression :
    YieldExpression
    ArrowFunction
    LeftHandSideExpression = AssignmentExpression
    LeftHandSideExpression AssignmentOperator AssignmentExpression
    BitwiseANDExpression : BitwiseANDExpression & EqualityExpression
    BitwiseXORExpression : BitwiseXORExpression ^ BitwiseANDExpression
    BitwiseORExpression : BitwiseORExpression | BitwiseXORExpression

If you use braces, then the inner part of ConciseBody will be a FunctionBody, which is a list of statements. So a ThrowStatement is allowed.

Why we have to wrap throw with brackets in es6 arrow functions

1 Answers1