-
Notifications
You must be signed in to change notification settings - Fork 157
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
get_dim_vector in manipulator #383
Conversation
dcb970b
to
55829af
Compare
1aec215
to
6eec313
Compare
6abfd93
to
5786a13
Compare
6eec313
to
c5ca27f
Compare
7f08bba
to
e07af2f
Compare
bfe63e5
to
4ebf55a
Compare
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.
I personally have nothing against getDimensions. Dimensions has been the word used in highfive since ever afaik. Switching to a synonym like “shape” is a matter of taste so IMO we shouldn’t do it as would break api and consistency. Further it makes it sound like a property, something that has been avoided in Highfive, hence most public methods start with a verb.
If however you introduce a getNumberOfDimensions I agree with that naming (including the “of”)
Makes sense. But then why not harmonise the internal and external naming:
? |
|
|
I would prefer ndim since it's a short for dimensions. Also, the fact that it is the same as numpy is nice |
Agreed! |
Should I change it? |
So, last version is |
No description provided.