Proposal: arbitrary &-inheritance.

[egasimus]

One of the main reasons I use a preprocessor is rule nesting - I really fell in love with that feature! However, it easily introduces unnecessary selector specificity, which can be a reason to entirely abandon one of the major conveniences of using a CSS preprocessor - if you care about writing optimized code, that is.

I propose extending the & operator's behavior to work at any point in the selector string. This way,

.lol {
    &-wut {
        ...
    }
}

would compile to:

.lol-wut {
    ...
}

And you wouldn't have to do this:

.lol {
}
    .lol-wut {
    }

Any opinions?

[Inkdpixels]

A possible usecase for this feature would be plugin / extension namespaces in templates.

[Anahkiasen]

This will probably be taken care of by the refactor of the & selector. At least I think (hope) so.

[nex3]

Subset of #286.