-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Deprioritized array interface #2338
Conversation
Should be merged after #2329. Should also reenable the Graph test that was disabled in that PR. |
Agreed this is overdue. #2329 is now merged so those tests should be re-enabled and the tests seem to have failed right now. Maybe fixing that (or a rebase) will get the tests green so I can merge? I'm a little worried that this change might cause problems as it affects so many things. But I also believe we really should do it now... |
It's revealing at least a few bugs caused by the ArrayInterface, which should be fixed by using the other interfaces. Tests also need updating because type comparisons are failing. |
56324c2
to
4186e68
Compare
d0ab568
to
7d092aa
Compare
7d092aa
to
43542f4
Compare
Had to make some fixes to the testing code in nbpublisher, it errored before it could capture test data. |
Ready to merge. |
Looks good. I think this is important to do and hope it won't cause us any backwards compatibility headaches! Merging. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Finally implements #1236, this is long overdue since the ArrayInterface mostly just causes troubles due to mixed types. With this change you should only ever end up with an ArrayInterface when you pass in an
NxM
array explicitly.