-
Notifications
You must be signed in to change notification settings - Fork 22
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
Unclear rotation names #76
Comments
I agree: I think this would be clearer. |
I have some free time and I think I can do this. |
That would be a solid clarity improvement |
@GuimilXD Just saw your message; if you haven't done it yet I've already started/am mostly done. |
Oh no! I'm also mostly done. For consistency's sake, I thought of changing |
I've adjusted them likewise (see #78). I'm not sure whether/when to use abbreviations though. |
I was also unsure when to use abbreviations. |
I just noticed your additional context, I hoped no one noticed my confusion on my own code :P |
Fixes #76 Open question: Should the functions be - spelled out: `clockwise`/`counter_clockwise` - abbreviated: `cw`/`ccw` - abbreviated only in compounds: e.g. `clockwise()` and `rotate_ccw_around()` --------- Co-authored-by: Félix Lescaudey de Maneville <felix.maneville@gmail.com>
Is your feature request related to a problem? Please describe.
Rotation functions are named
left
/right
and similar. This is confusing – what do left/right have to do with rotations, which direction is which? In fact, the documentation for these functions does not use these terms, it instead usesclockwise
/counterclockwise
, which are clear.Describe the solution you'd like
Deprecate these functions and replace them with
clockwise
/counterclockwise
and similar.Alternatively this could be abbreviated as
cw
andccw
(as e.g.rotate_counter_clockwise
is rather long).Additional context
example of confusion
The text was updated successfully, but these errors were encountered: