➜

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 anon
Recipients anon, hct, josh.r, mark.dickinson, martin.panter, meador.inge, pitrou, rhettinger, serhiy.storchaka, tim.peters, vstinner
Date 2014-10-02.10:18:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412245087.41.0.966972273957.issue19915@psf.upfronthosting.co.za>
In-reply-to
Content 
Pros for x.bits being a view:
- seems slightly cleaner (in my opinion)
- can potentially abstract slicing bits without copying the underlying int (e.g. x.bits[2:][4:])

Pros for x.bits being a function:
- Victor's point
- no need to depreciate x.bit_length
- no need to create a View object and probably faster?
- easier to implement
History
Date User Action Args
2014-10-02 10:18:07anonsetrecipients: + anon, tim.peters, rhettinger, mark.dickinson, pitrou, vstinner, meador.inge, martin.panter, serhiy.storchaka, hct, josh.r
2014-10-02 10:18:07anonsetmessageid: <1412245087.41.0.966972273957.issue19915@psf.upfronthosting.co.za>
2014-10-02 10:18:07anonlinkissue19915 messages
2014-10-02 10:18:07anoncreate