Change `space_elem == other` behavior?

[kohr-h]

We differ from Numpy in the way we interpret ==. Our use case has quite limited usability, and Numpy users will be surprised by the interpretation.
Another issue that comes with this difference is our current inability to do things like x[x > 0] = 1 or so, which would be nice to have. Then, of course, == cannot be an exception.

Question: How about we change our tensors to behave like Numpy arrays in that respect?

[adler-j]

I frankly vote yes for this. My suggestion is as follows: simply bypass of of these by making

def __eq__(self, other):
    return np.equal(self, other)

and equivalently for the others.