Message195665
A lot of this discussion has flown a rather unfortunate distance over my head, especially since I've barely had time to follow it. But it looks to me like--given the number of other places that do the same thing as operator.index currently does--there needs to be a simple way to do the right thing somewhere accessible, which probably means a builtin.
On the other hand, it seems to me like 'a.__index__()' *should* be "the right thing" to do, but I get the feeling that making that so would be an astronomically huge change without much real benefit and lots of opportunities to break everything. I suspect I'm also missing something fundamental in why it's not the right thing to do. |
|
Date |
User |
Action |
Args |
2013-08-19 20:43:39 | zach.ware | set | recipients:
+ zach.ware, arigo, mark.dickinson, eric.snow, serhiy.storchaka |
2013-08-19 20:43:39 | zach.ware | set | messageid: <1376945019.56.0.78825280255.issue18712@psf.upfronthosting.co.za> |
2013-08-19 20:43:39 | zach.ware | link | issue18712 messages |
2013-08-19 20:43:39 | zach.ware | create | |
|