Parameter names break function type parsing

[VirtualButFake]

When parsing a script that contains a function type definition containing a parameter name, Loretta does not parse this correctly

You can reproduce this by trying to parse i.e.:

export type a = (p1: any) -> any

Expected behaviour would be to parse it properly, preserving parameter names
Issue occurs on all syntax options

[VirtualButFake]

I'd like to expand this issue to also contain the following case:

((Player, ...any) -> ...any)?)

This causes the following errors:

I can't place why but it seems to be related to this.

[GGG-KILLER]

I'd like to expand this issue to also contain the following case:

((Player, ...any) -> ...any)?)

This causes the following errors: I can't place why but it seems to be related to this.

does this fail with the code

export type a = ((Player, ...any) -> ...any)?)

?

[VirtualButFake]

I'm not able to test for the coming few days - but I'd assume so, considering that type errored when it was used as function return type

[TheGreatSageEqualToHeaven]

Sorry I've been busy I'll take a look at this the coming week.