Message308787
Here's another idea: have a new type field (a tp_something) that exposes the GC priority for this type. It could be an integer between -8 and 7, for example (0 being the default). Then tp_finalize would be called in sorted priority order.
The tricky part of course is to make this acceptable performance-wise (i.e. avoid walking the collectable list 16 times, once for each priority level). For example by creating bucket lists for each priority level (only for objects with a non-NULL tp_finalize). |
|
Date |
User |
Action |
Args |
2017-12-20 19:30:57 | pitrou | set | recipients:
+ pitrou, tim.peters, nascheme, vstinner, nikratio, neologix, martin.panter, serhiy.storchaka, xgdomingo, nitishch |
2017-12-20 19:30:57 | pitrou | set | messageid: <1513798257.65.0.213398074469.issue17852@psf.upfronthosting.co.za> |
2017-12-20 19:30:57 | pitrou | link | issue17852 messages |
2017-12-20 19:30:57 | pitrou | create | |
|