Hello Don,

The current rule is:
x OP y      means
cast(CommonType!(x,y))x OP cast(CommonType!(x,y))y
for any binary operation OP.
How can we fix >>> without adding an extra rule?

However it's not that way for the ternary op, so there is a (somewhat related) precedent.

Even considering RHS<0, I would NEVER /expect/ a shift to have any type other than typeof(LHS).
--
... <IXOYE><



Reply via email to