skef
skef
If we go the direction of this condition tree, the proposal on the mailing list was to: 1. Update the VARC condition spec and the (new, so easily alterable) LookupVarriation...
> Also we would have to define a stack limit. Is there really a substantial difference between the depth of a postfix operator expression and the depth of an offset-based...
Functionally, a `ConditionSet` doesn't identify itself or otherwise act like a condition, so it can't serve the job of ANDing the conditions in any other position in an expression tree...
Each of these would be a new condition format, so instead of the current working draft proposal of format 1 (the current), format 2 (its negation), format 3 (condition value),...
Offset 0 is at least somewhat magical in some contexts. I thought I recalled one or two other cases with non-zero offsets not treated as offsets but I'm not recalling...
I suppose the argument here is going to boil down to "This is like COLR v1 so it's better from a simplicity standpoint". That will probably win the day, but...
I just chose postfix because it tends to be more familiar. If there are engineering reasons to do prefix it should be prefix.
Alright, consider my concerns addressed.
@behdad could we just do away with empty ConditionAnd and ConditionOr tables? I can't think of any function they would serve and what I'm seeing in the proposal about them...
Seems like the main question that's been raised on the email lists but not here is whether DMAP should have some means of negative mapping -- a means of ignoring...