-
Notifications
You must be signed in to change notification settings - Fork 55
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
feature ndim #577
feature ndim #577
Conversation
Codecov Report
@@ Coverage Diff @@
## master #577 +/- ##
=======================================
Coverage 96.47% 96.47%
=======================================
Files 75 75
Lines 15161 15169 +8
=======================================
+ Hits 14626 14634 +8
Misses 535 535
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
YES! 👏
I'd be for not going through numdims though. In fact, I'd be for deprecating numdims and removing it before v1.0. What do you think?
I think so, too. Neither Numpy nor Pytorch use 'numdims'. ndim should be the preferred method name. Pytorch's equivalent function is called dim(). ndim() and ndimension() are two aliases I'm aware of. Should we add them? I don't think that we need those as we're striving for numpy API compatibility. |
Description
Add method ndim to dndarray for NumPy-API-compatibility. Will replaces numdims()
Issue/s resolved: None
Changes proposed:
Type of change
New feature
Due Diligence
Does this change modify the behaviour of other functions? If so, which?
no