# use commutative in a sentence.

The real question is: can it do *commutative* diagrams?

It's not *commutative*: -0 + 0 = -0, but 0 + -0 = 0.

I agree, if by "causality" you mean "implication" and by "*commutative*" you mean "transitive".

And thus forces programmer to think about the order of non-*commutative* operations.

Floating point addition and multiplication are *commutative*, but are not necessarily associative.

Best bet is to replace x÷y by x*(1/y) as division is not *commutative* while multiplication is *commutative*.

I'm not a huge fan of "+" for string concatenation as "+" is, traditionally, *commutative*; I like Lua's "..

I gotta agree with you on translation not being *commutative*.

Do we have two category theorists here, or has the unlikely happened and *commutative* diagrams found an application in the real world?

One of the strangest things about == is that although it's *commutative*, it's not transitive: 0 == '0' // true
0 == '' // true
'0' == '' // false

Take a look at *commutative* replicated data types (crdt) as a little known alternative to OT:

Sublime is generally great, but it desperately needs one fix before I'll ever really love it: make page up/down *commutative*.

Might have been better to demonstrate that using subtraction as addition is *commutative* and thus either one works fine in this case.