paul@316 | 1 | Where attribute combinations do not yield objects
|
paul@316 | 2 | (tests/abandoned_attribute_usage_multiple_candidates.py) in
|
paul@316 | 3 | Importer._collect_attributes, the individual attributes should be exposed,
|
paul@316 | 4 | since it is apparent that no single object type can satisfy the reported
|
paul@316 | 5 | combination, and thus a guard will not be generated.
|
paul@316 | 6 |
|
paul@310 | 7 | Loop entry points should capture usage to update later assignments in the loop.
|
paul@310 | 8 | The continue and break statements should affect usage propagation.
|
paul@304 | 9 |
|
paul@304 | 10 | Constant attribute users need not maintain usage since they are already resolved.
|
paul@304 | 11 |
|
paul@304 | 12 | Consider handling CallFunc in micropython.inspect in order to produce instances of specific classes.
|
paul@304 | 13 | Then, consider adding support for guard removal/verification where known instances are involved.
|
paul@304 | 14 | Consider handling branches of values within namespaces in order to support more precise value usage.
|