Possible to output invalid CSS with a @function

[chriscoyier]

input.scss

@function test() {
  @if (false) {
    @return 0;
  } @else {
    opacity: 1;
  }
}

.my-module {
  opacity: test();
}

Actual results

Libsass 3.5

.my-module {
  opacity:   opacity: 1; }

Expected result

Throw an error like

Functions can only contain variable declarations and control directives.

http://libsass.ocbnet.ch/srcmap/#QGZ1bmN0aW9uIHRlc3QoKSB7CiAgQGlmIChmYWxzZSkgewogICAgQHJldHVybiAwOwogIH0gQGVsc2UgewogICAgb3BhY2l0eTogMTsKICB9Cn0KCi5teS1tb2R1bGUgewogIG9wYWNpdHk6IHRlc3QoKTsKfQo=

Spec sass/sass-spec#1218

[xzyfer]

Thanks @chriscoyier. This is an issue with how we validate @else blocks.

[chriscoyier]

This probably isn't the perfect place to ask this, so feel free to shoo me there.

I'm curious how the rollouts work. This eventually goes into a point release for libsass, right? Then implementations of it need to update to that version, so if we're using Node, we wait for the next point release of node-sass?

[xzyfer]

Yep that's pretty much how it goes. Luckily I'm the maintainer of node-sass also so the turn around is pretty fast once we make a LibSass release.