& selector creates new scope within same selector path

[twhoff]

Using the ampersand to create an anonymous scope within a selector in LESS4J creates duplicate selectors in the CSS output, where in Node LESS, the output is still grouped under a single selector. Duplication causes larger compiled files and seems to take more time to compile as well... could be an issue with how LESS4J handles scope?

Simple example:

.test {
    .test-mixin();
    & {
        @value: 2;
        value: @value;
    }
    value: @value;
}

.test-mixin() {
    @value: 1;
}

Compilation result:

// Node LESS - correct

.test {
  value: 2;
  value: 1;
}

// LESS4J - duplication

.test {
  value: 1;
}
.test {
  value: 2;
}