-
Notifications
You must be signed in to change notification settings - Fork 4
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
question about Arange function #12
Comments
FYI: Reviewing this issue revealed an inconsistency that was fixed in b9dc613. Some of the numpy arange logic has been a pain point for me and those I've taught/worked with. The issue shows up when working with negative-stepping ranges:
The other part of changing the
While I would like to mirror as much of the numpy API as possible, the handling of negative-stepping ranges is something I felt needed to be re-thought. If you have suggestions on how to improve the API, please keep in mind that |
Thanks for your consideration.
Now we just need to handle 'stop', leaving 'start' unchanged. Thanks. |
Hi,
In numgo, fmt.Println(numgo.Arange(0, 10)) => [0 1 2 3 4 5 6 7 8 9 10].
In numpy, print(np.arange(0, 10)) => [0 1 2 3 4 5 6 7 8 9].
Both are ok, but I prefer to drop 'stop', like numpy.
Would you think about it?
Tks!
The text was updated successfully, but these errors were encountered: