➜

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 cowlicks
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:17:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461601054.83.0.464424357477.issue19251@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2016-04-25 16:17:35cowlickssetrecipients: + cowlicks, gvanrossum, georg.brandl, rhettinger, terry.reedy, gregory.p.smith, pitrou, vstinner, christian.heimes, socketpair, Ramchandra Apte, martin.panter, serhiy.storchaka, abarnert, josh.r
2016-04-25 16:17:34cowlickssetmessageid: <1461601054.83.0.464424357477.issue19251@psf.upfronthosting.co.za>
2016-04-25 16:17:34cowlickslinkissue19251 messages
2016-04-25 16:17:34cowlickscreate