-
Notifications
You must be signed in to change notification settings - Fork 2.2k
add typedef to get element type of array_t #632
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
Comments
Seems reasonable. Minor nitpick: maybe |
sure
…On Tue, Jan 31, 2017 at 3:56 PM Jason Rhinelander ***@***.***> wrote:
Seems reasonable. Minor nitpick: maybe value_type rather than el_t?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#632 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHK0D8VLpUUy6v1QCldDAdmlo4zzFkVks5rX5_hgaJpZM4LzJyV>
.
|
Looks reasonable. |
dean0x7d
added a commit
to dean0x7d/pybind11
that referenced
this issue
Mar 13, 2017
dean0x7d
added a commit
that referenced
this issue
Mar 13, 2017
* Add value_type member alias to py::array_t (resolve #632) * Use numpy scalar name in py::array_t function signatures (e.g. float32/64 instead of just float)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe this makes it a lot easier to write generic code using array_t
The text was updated successfully, but these errors were encountered: