Basic syntax question about engine

[bergie]

@vovakkk you cannot use a class selector on both sides of a constraint, since each of those can return multiple elements. One of them should be an id selector so we make sure the rules are solvable

[bergie]

@d4tocchini something for later, but maybe we should actually run the queries before throwing the error above? That way we could have the rule working as long as there is only one element with that class.

[cirvladimir]

Whats wrong with having multiple elements on both sides? This equivalent code is fine:

.a1[width] == [X] == .a2[width];

and has the same declarative meaning.

[d4tocchini]

imagine an array of variables constrained to equal another array of variables. Does each left side variable constrained to each one on the right? Does it only constrain vars with the same index? What happens when one array has less vars then the other? Wasn't comfortable about this... With a single variable bridging the two arrays, you don't have the above uncertainty.

[cirvladimir]

I see. That makes sense.