## Comments

    // Single line comment
    /* Multi-line
    comment */

## Variables

    @nice-blue: #5B83AD;
    @light-blue: @nice-blue + #111;

## At-rules

    @media screen and (min-width: 320px) {}

## Mixins

    .bordered {
      border-top: dotted 1px black;
      border-bottom: solid 2px black;
    }
    #menu a {
      .bordered;
    }
    #header a {
      color: orange;
      #bundle > .button;
    }

## Mixins with parameters

    .foo (@bg: #f5f5f5, @color: #900) {
      background: @bg;
      color: @color;
    }
    .bar {
      .foo();
    }
    .class1 {
      .mixin(@margin: 20px; @color: #33acfe);
    }
    .class2 {
      .mixin(#efca44; @padding: 40px);
    }

## Interpolation

    @mySelector: banner;
    .@{mySelector} {
      font-weight: bold;
    }
    @property: color;
    .widget {
      @{property}: #0ee;
      background-@{property}: #999;
    }

## Known failures

There are certain edge cases where Prism will fail. There are always such cases in every regex-based syntax highlighter. However, Prism dares to be open and honest about them. If a failure is listed here, it doesn’t mean it will never be fixed. This is more of a “known bugs” list, just with a certain type of bug.

### At-rules looking like variables

    @import "some file.less";

### At-rules containing interpolation

    @import "@{themes}/tidal-wave.less";

### extend is not highlighted consistently

    nav ul {
      &:extend(.inline);
      background: blue;
    }
    .a:extend(.b) {}