-
Notifications
You must be signed in to change notification settings - Fork 21
Closed
Description
I ran into this today, is there any reason (apart from code size and compile time) against supporting, e.g., also 5 and 6 dims?
Lines 170 to 184 in 1c065b1
| const auto dispatch = [](const py::array_t<T> &src_, View &&dst_) { | |
| switch (src_.ndim()) { | |
| case 0: | |
| return copy_flattened_0d<convert>(src_, std::forward<View>(dst_)); | |
| case 1: | |
| return copy_flattened_1d<convert>(src_, std::forward<View>(dst_)); | |
| case 2: | |
| return copy_flattened_2d<convert>(src_, std::forward<View>(dst_)); | |
| case 3: | |
| return copy_flattened_3d<convert>(src_, std::forward<View>(dst_)); | |
| case 4: | |
| return copy_flattened_4d<convert>(src_, std::forward<View>(dst_)); | |
| default: | |
| throw std::runtime_error("Numpy array has more dimensions than supported " | |
| "in the current implementation."); |
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done