Destructuring with single-line 'for' fails

This parses:

for {:file, :args} in *options.runFiles
  runFile file, args 

But this doesn't:

runFile file, args for {:file, :args} in *options.runFiles

Failed to parse:
 [107] >>    runFile file, args for {:file, :args} in *options.runFiles

[Idyllei]

I believe that the second argument it being misread. Instead of being read correctly, it is looking for a comprehension because of the for-loop decorator, but doesn't know what to do.

It seems to me that your current code is being read as a comprehension:

runFile file, {args for {:file, :args} in *options.runFiles}
-- or:
runFile file, [args for {:file, :args} in *options.runFiles]

But it may not know which you want (if you want it at all).

Try this:

runFile(file, args) for {:file, :args} in *options.runFiles

The parentheses should disambiguate for the linter.

That didn't parse either. However, it does parse without destructuring. with and without parentheses.

runFile info.file, info.args for info in *options.runFiles

...which is ultimately what I ended up going with, for the sake of one-linededness.

Destructuring simple arrays (e.g., stuff a, b, c for {a, b, c} in *things) fails as well. So the issue does seem to specifically coincide with one-liners and destructuring, as far as I can tell. Maybe more test cases are needed?

[leafo]

This is indeed broken, doesn't work for comprehensions as well:

[{a,b} for {a,b} in *thing]