New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Shapes gives counterintuitive results #421
Comments
So there are two unrelated issues here. First, that currently you can do Second, the idea of overloading the |
I agree it's a bad idea. We should stop implementing extraneous operators for |
Should we preserve comparing |
Where? |
Oh sorry, you mean comparing for equality, not for ordering. Yeah let's preserve that, we can always deprecate it later if it turns out to cause issues. |
Shape
s implement__add__
, but adding them is currently not useful:The expected result here (I argue) would be
(48, False)
, but (probably becauseShape
is a named tuple under the hood) we get the not-very-useful result shown above.Obviously in this case you can do
(x+y).shape()
but that's not always easy or possible (I hit a particular case involving anEnum
)The text was updated successfully, but these errors were encountered: