Default mixin arguments aren't recognized by selector guards

[radium-v]

Howdy,

I'm trying to use a guarded selector inside a mixin with default vars, like so:

.a(@v: 0) {
    & when (@v >= 0) {
        prop: @v;
    }
}

.b {
    .a;
}

Changing .b will allow it to pass though:

.b {
    @v: 0;
    a;
}

Also, changing the mixin works:

.a(@v: 0) {
    .c(@v) when (@v >= 0) {
        prop: @v;
    }
    .c(@v);
}

.b {
    .a;
}

My expectation would be that example 1 would output the prop for .b by default, since the mixin sets its local var @v: 0, but it throws an undefined error.

There's not much documentation around the new features in v1.5.0, so I might be doing it wrong, but it feels like a bug. Thoughts?

[radium-v]

One extra note: the variable is indeed visible within the mixin's scope:

.a(@v: 0) {
    & {
        prop: @arguments;
    }
}

.b {
    .a;
}

Will output:

.b {
    .prop: 0;
}

[lukeapage]

It works the same way two mixins would work.. the first call unlocks the
2nd. Then it is only called once in its final scope. I agree its not very
obvious though and we may need to look at the scoping rules to improve this
new feature.

[lukeapage]

re-reading I think we should fix sorry.

[lukeapage]

Sorry should have fixed this ages ago