Message205743
> I think slicing semantically "seems wrong" but it might be more elegant. It might also make catching errors harder (in the case where an int is sent to a function that does slicing and now won't fail with a TypeError).
not sure what's semantically "seems wrong" with it. not sure why TypeError or any other error catching should come into play for this.
calling a function is way more expensive than doing bit shift and/or AND operation. as a function, you've only hide your code into Python binaries at the expense of performance |
|
Date |
User |
Action |
Args |
2013-12-09 22:27:55 | hct | set | recipients:
+ hct, tim.peters, rhettinger, mark.dickinson, pitrou, vstinner, meador.inge, serhiy.storchaka, anon |
2013-12-09 22:27:55 | hct | set | messageid: <1386628075.3.0.793599888988.issue19915@psf.upfronthosting.co.za> |
2013-12-09 22:27:55 | hct | link | issue19915 messages |
2013-12-09 22:27:55 | hct | create | |
|