Weird results of comparison of non-numeric types with <, > and similar operators.

[seven-phases-max]

(this is more like a self-note that the comparison subsystem probably needs some not-so-minor refactoring).
Example:

.test {
    & when (two < 1) {
        1: true;
    }

    & when (a > b) {
        2: true;
    }

    @v: whatever complex "thing", 3;
    & when (@v < ~"3") {
        3: true;
    }

    & when (#fff < #000) {
        4: true;
    }

    // etc.
}

Result:

.test {
  1: true;
  2: true;
  3: true;
  4: true;
}

Expected result: error? false?

Related issues: #1725 (comment)

[lukeapage]

Yes, ive noticed this before. My vote is it should return false. The
current line is that a mixin should use the is functions if doing a <, >
comparison.

[seven-phases-max]

Closing as fixed in v2. All return false now.