-
Notifications
You must be signed in to change notification settings - Fork 85
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
ar != None unexpected behaviour #487
Comments
There's a whole discussion of this issue, starting at #490 (comment) When I wrote it there, I thought I was narrowly saving it from oblivion because I only remembered hearing it on Slack. I could have just pointed to this issue. Anyway, the cross-reference will be useful in solving it. |
(I'm going through old issues, deciding what to do with them.) I think that the ak.Array([1, 2, None, 3, None, 4]) == None return ak.Array([False, False, True, False, True, False]) then someone else's use-case might break because they were assuming that ak.Array([1, 2, None, 3, None, 4]) + 10 returns ak.Array([11, 12, None, 13, None, 14]) That is, the scalar ak.Array([1, 2, None, 3, None, 4]) == None would be ak.Array([False, False, None, False, None, False]) because each @agoose77, do you concur? If you think there is something that we should do that would benefit all use-cases, reopen the issue. Thanks! |
@jpivarski I had the same thought. If we allow |
Using
ar != None
results in an unexpected maskConsider:
Expected behaviour:
such that
The text was updated successfully, but these errors were encountered: