This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Alexander.Belopolsky
Recipients Alexander.Belopolsky, Arfrever, Dag.Sverre.Seljebotn, belopolsky, christian.heimes, georg.brandl, loewis, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-09-03.20:21:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7h-xbCC_GWbTtP3JOFzmFmwWXyoa_3mkbh4jEPJxwHqK2=NQ@mail.gmail.com>
In-reply-to <50450C05.4010505@v.loewis.de>
Content
On Mon, Sep 3, 2012 at 3:59 PM, Martin v. Löwis <report@bugs.python.org> wrote:
> if hashing was restricted
> to contiguous bytes, then the implementation would certainly be
> simplified quite a bit: currently, if it's not contiguous, it needs
> to make a separate copy and hash that.

I would be happy if this whole business of "strided" memory layouts
would go away.  I find it to be a failed attempt of
over-generalization.  It is failed because it does not cover many
important formats even in 2-d: sparse matrices, symmetrical matrices,
banded matrices, etc., etc.  (Check level 3 BLAS or NAG for a longer
list.)  It is an over-generalizarion because in practice it is often
more efficient to gather your data in contiguous memory, perform
vector calculations and then scatter the results than to operate on
scattered data to avoid copying.

I would much rather see a generalization of suboffsets that would
allow me to have views into arrays of pointers to variable width
arrays than strides.
History
Date User Action Args
2012-09-03 20:21:49Alexander.Belopolskysetrecipients: + Alexander.Belopolsky, loewis, georg.brandl, mark.dickinson, ncoghlan, belopolsky, pitrou, vstinner, christian.heimes, Arfrever, skrah, meador.inge, python-dev, Dag.Sverre.Seljebotn
2012-09-03 20:21:49Alexander.Belopolskylinkissue15814 messages
2012-09-03 20:21:48Alexander.Belopolskycreate