Mixin defintion arguments: whitespace works as delimiter

[seven-phases-max]

I occasionally stepped into this bogus:

.mixin(@a @b) {
    args: @a @b;  
}

x {
    .mixin(x, y);  // OK -> args: x y;
}

I.e. the supposedly invalid mixin definition .mixin(@a @b) is actually interpreted as being equal to .mixin(@a, @b) and .mixin(@a; @b).

Other curious side-effects are:

• .m(@a @b, @c) -> .m(@a, @b, @c)
• .m(@a @b; @c) -> .m(@b, @c)
• .m(@a; @b @c) -> .m(@a, @b, @c)
• .m(@a; @b, @c) -> .m(@a, @c)
• .m(@a, @b @c) -> .m(@a, @b, @c)
• etc.

[matthew-dean]

Huh. Interesting.

[seven-phases-max]

Yeah, I was just looking for some syntax that could pass the parser to mimic:

.for-each(@value in @list) {...}

(or a sort of) and ooops, found it's already a passable syntax :) (the evaluation part within a plugin will be quite tricky since it has to be a pre-evaluation visitor, but that's another story).