Broken syntax when using function type as a function argument

[tomaskallup]

It's really hard to describe for me, so here are pictures:
Without typing resolve argument (proper highlight):

Syntax groups at the const validationResult....:
['typescriptClassBlock', 'typescriptBlock', 'typescriptFuncCallArg', 'typescriptBlock', 'typescriptVariable']

With typing the resolve as a function (broken highlight after void):

Syntax groups at the const validationResult....:
['typescriptClassBlock', 'typescriptBlock', 'typescriptFuncCallArg', 'typescriptObjectLiteral', 'typescriptObjectL abel']

The typescriptBlock seems to break after void) => { and it starts to thinks it's a object literal. I would fix this, but I'm not sure where to look.

EDIT: It's the second arrow (=>) which breaks, it looses typescriptArrowFuncDef for some reason... the space right before it still has it

[HerringtonDarkholme]

It is not supported.

YATS uses regex to tell if a paren is arrow function paren or not. However, it is hard to write a regex to support multiline arrow function with type annotation, if possible. Plus, the performance of such regex is probably disappointing.

So I just give up supporting annotated arrow function.

[tomaskallup]

Oh I see, for stuff like this it's nicer to have the type stored somewhere in a type as it makes the code more readable.