computing the resulting inventory from the merge changeset

[duchier at ps.uni-sb.de]

Aaron Bentley <aaron.bentley at utoronto.ca> writes:

> I don't think we have a style rule about it, but we use != everywhere
> else in the code.  <> isn't intuitive to me, because some things that
> are different have no obvious ordering.  I didn't even know Python
> supported that form.

Ok, I'll change it.  I suspect that, when I originally learned Python,
the != operator hadn't yet made it into the language. <> is also used
in Pascal. re: "no obvious ordering": a partial order that is also not
total will have elements that have no obvious ordering.  The way I
read <> is "neither one precedes/dominates the other".  For a flat
partial order (e.g. a degenerate semi-lattice), this coincides with
non-equality.

Cheers,

--Denys