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