->! parsed as operator

[michaellilltokiwa]

Might be a bit surprising that ->! is parsed as an operator.
May be it is more reasonable to always consider ->... as the lambda arrow + start of a new expression.

ex =>

  [true]
    .filter x->!x

/home/sam/playground/test.fz:4:13: error 1: Could not find called feature
    .filter x->!x

Feature not found: 'x' (no arguments)
Target feature: 'ex'
In call: 'x'
Lambda operator is part of infix operator here:
/home/sam/playground/test.fz:4:14:
    .filter x->!x

To solve this, add a space after '->'.

one error.

[fridis]

Yes, this is surprising, but it is somewhat arbitrary to automatically split off ->, other operators with special handling then might need the same treatment like =>, :=, ., |, .., ..., :, !, maybe some more.

I think the simple rule that a sequence of a letter followed by letter/digit is always an identifier (unless this forms a keyword), while a sequence of operator codepoints is always an operator (unless it is a special operator) is nice to have.

What we can enhance, however, is the error message in this case, it should also suggest using parentheses (/).