Message276411
| Author | skrah |
|---|
| Recipients | benjamin.peterson, christian.heimes, doko, ned.deily, serhiy.storchaka, skrah, vstinner, ztane |
|---|
| Date | 2016-09-14.10:01:53 |
|---|
| SpamBayes Score | -1.0 |
|---|
| Marked as misclassified | Yes |
|---|
| Message-id | <1473847313.49.0.394099287528.issue28055@psf.upfronthosting.co.za> |
|---|
| In-reply-to | |
|---|
| Content |
|---|
I see. No, most NumPy arrays are C-contiguous. Multi-dimmensional arraysare contiguous, too.Non C-contiguous arrays arise mostly during slicing or if they'reFortran-order to begin with.But NumPy aside, it's weird to have slice of a huge regular bytes view(this particular slice is still C-contiguous) that is suddenly copiedbecause the alignment requirements changed.I really prefer a simple rule for memoryview: If the data is C-contiguous,you get the fast path. |
|