Dag Sverre Seljebotn, 26.10.2009 19:59:
> a) Me and Kurt decided to use the name "memoryview" everywhere in the
> code written in summer. The essential feature of the proposed Cython
> type described in enhancements/array is a) a view to a reference-counted
> PEP 3118 buffer, b) slices returns new sub-views. This is exactly what
> the Python memoryview type does. Cython adds static typing to this, but
> we decided to also name the Cython concept memoryview.
Is it just the "concept", or also the type itself?
I just want to make sure people can
cdef memoryview m
to use the Python memoryview type without having it fail or do something
unexpected, just like they use
cdef list l
> b) There was a recent discussion on numpy-discuss where people reacted
> on using the term SIMD for anything but CPU SIMD (i.e. many people
> understand "Instruction" in SIMD to refer exclusively to CPU
> instructions). Some voiced opposition to this view as well, but to avoid
> any ambiguity I suppose "vectorized operation" is the most neutral
Fine with me.
Stefan
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev
