Support for throw expressions

[verekia]

const fn = () => true ? throw 'true' : throw Error('false')

causes Unexpected token throw.

https://github.com/tc39/proposal-throw-expressions (stage 2)

[friday]

That's because you're returning it. You can't return throw.

[verekia]

const a = true ? throw 'true' : throw Error('false')

causes the same issue.

[friday]

Sorry. My bad! I thought you were just mistaking throw statements and was really confused why you added this to the ES2015 & 2016 meta-issue.

[Zvax]

Not sure if that's the same issue, but I come upon the same error message when using this (I don't believe that being in a constructor has any effect on it, probably any context would be the same, but it's how I encounter it):

constructor() {
    this.param = process.env.ENVIRONMENT_VARIABLE || throw new TypeError(`The ENVIRONMENT_VARIABLE should be set in the environment.`)
}

I use this because I find it nice, and because I want to prevent an object from being instantiated if some values are not present in the environment. There are more verbose ways to achieve that that do not throw flow off, but I would find it neat to keep it that way!