Agree and streamline treatment of context in tensor

[tensorics]

Agree and streamline treatment of context in tensor

[agorzawski]

for the first bullet, yes it it shouldn't be taken (i.e. two chroma measurements at different time (the time is in the context).... isIdentical() seems to be the most obvious .

second bullet, I vaguely remember that it was implemented. To be confirmed...

[michi42]

• I think I agree on the first point - two tensors can be equal even with different contexts. So it should not be considered for equals(). Adding an identical() method or similar sounds fine. We only need to take care that this is reflected for hashCode() as well to not break the contract.
• For the broadcasting, I would not consider the context for the default broadcasting strategy. In particular not when we define the equals() without context. Otherwise, we could produce 'interesting' results like A==B but A+C != B+C if A and B have different contexts.
  In general, one could ask how much sense it makes to propagate forward the context through calculations ... what should be the context of A+B if A and B have different contexts?
  The current (default) LeftContextPreservedStrategy feels somewhat arbitrary - and, strictly speaking, breaks the commutativity of operations (in particular as long as we consider the context for equals()).
  Perhaps propagating no context at all through calculation would be a better default? Or at least don't propagate contexts in a way that breaks when constructing the result tensor.

[kaifox]

Ok, ... I think here we converge more or less in our opinions....