➜

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 gvanrossum
Recipients Ramchandra Apte, abarnert, christian.heimes, cowlicks, georg.brandl, gregory.p.smith, gvanrossum, josh.r, martin.panter, pitrou, rhettinger, serhiy.storchaka, socketpair, terry.reedy, vstinner
Date 2016-04-25.16:27:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJLvfvwtcn7YzkVgf+HVjOprmiRj3KupATsfzQ2mFj5-0g@mail.gmail.com>
In-reply-to <1461601054.83.0.464424357477.issue19251@psf.upfronthosting.co.za>
Content 
Can you point to some examples of existing code that would become more
readable and faster when this feature exists? Separately, how is it more
secure?

On Mon, Apr 25, 2016 at 9:17 AM, cowlicks <report@bugs.python.org> wrote:

>
> cowlicks added the comment:
>
> To reiterate, this issue would make more readable, secure, and speed up a
> lot of code.
>
> The concerns about this being a numpy-like vector operation are confusing
> to me. The current implementation is already vector-like, but lacks size
> checking. Isn't "int ^ int" really just the xor of two arbitrarily long
> arrays of binary data? At least with "bytes ^ bytes" we can enforce the
> arrays be the same size.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue19251>
> _______________________________________
>
History
Date User Action Args
2016-04-25 16:27:38gvanrossumsetrecipients: + gvanrossum, georg.brandl, rhettinger, terry.reedy, gregory.p.smith, pitrou, vstinner, christian.heimes, socketpair, Ramchandra Apte, martin.panter, serhiy.storchaka, abarnert, josh.r, cowlicks
2016-04-25 16:27:38gvanrossumlinkissue19251 messages
2016-04-25 16:27:38gvanrossumcreate