UFCS issue iterator into macro about nimskull HOT 4 CLOSED

Ah, so from what I've understood, in order to not allow false programs to compile the way to do this at least for the time being is to keep it to the form like this :)

Yep, using the explicit call or command syntax works around the method-call syntax limitation.

In general, a.b and b(a) are not fully interchangeable, and whether that's going change or stay is not entirely clear at the moment.

from nimskull.

At the center of the problem is that for expression a.b, a is analyzed first, and if there's an error with it, b(a) is never attempted. The manual also has an entry regarding this limitation (toSeq is a template).

Edit: Sorry, I made a mistake reading the compiler debugger output, it's a classic AST corruption issue. The compiler already tries b(a) when a.b is an error.

Nonetheless, I consider this limitation to be a bug that needs to be fixed.

from nimskull.

The only way forward here seems to be always considering iterator symbols during overload resolution (they're currently only considered in certain contexts).

from nimskull.

Ah, so from what I've understood, in order to not allow false programs to compile the way to do this at least for the time being is to keep it to the form like this :)

import std/[sequtils]
let lines = to_seq "filename".lines

Thank you for looking into it and dealing with it so quickly, at least now I think I understand why it doesn't work, which is already a good thing :)

from nimskull.