Parser can't parse cast of a function call about lensorcompilercollection HOT 7 CLOSED

What happens if you do (foo) as! ... instead of foo() as! ...

from lensorcompilercollection.

5head, that works. So is this the way to cast function calls now? Doesn't look to bad tbh, but at least I didn't really find it idiomatic especially the case without the outside perens, where the vardecl is cast.

from lensorcompilercollection.

In general, a function call is (function ...args), like LISP. No parens for arguments are needed. And, the parens are just a paren expression, for grouping, so they are not always needed.

I'd agree there are still some edge cases I'm not happy with but I won't work on those until I get back onto Intercept itself (not LCC)

from lensorcompilercollection.

So maybe also label this with somekind of fix when somebody feels like it label? Or write it in todo
Would just be dumb if issues get rediscovered over and over again (I see myself doing that) and I don't want to search in closed issues for things that are potentially still issues

from lensorcompilercollection.

There is no issue here to fix. foo() is not a function call, it's a function followed by a paren expression.

Due to deproceduring, this would actually be a function call with the first argument as an empty paren expression

from lensorcompilercollection.

What is this then?

from lensorcompilercollection.

It looks like a screenshot from one of the parser source files of the compiler, all of which I did not write and am not working on right now.

from lensorcompilercollection.