paul@364 | 1 | Fix the attribute names in the report.
|
paul@364 | 2 |
|
paul@364 | 3 | Consider type deduction and its consequences where types belong to the same hierarchy
|
paul@364 | 4 | and where a guard could be generated for the most general type.
|
paul@364 | 5 |
|
paul@364 | 6 | Consider attribute merging where many attributes are just aliases for the same underlying
|
paul@364 | 7 | definition.
|
paul@364 | 8 |
|
paul@362 | 9 | Consider merging the InspectedModule.store tests with the scope conflict handling.
|
paul@362 | 10 |
|
paul@364 | 11 | Consider permitting multiple class alternatives where the attributes are all identical.
|
paul@364 | 12 |
|
paul@360 | 13 | Support class attribute positioning similar to instance attribute positioning, potentially
|
paul@360 | 14 | (for both) based on usage observations. For example, if __iter__ is used on two classes,
|
paul@360 | 15 | the class attribute could be exposed at a similar relative position to the class (and
|
paul@360 | 16 | potentially accessible using a LoadAttr-style instruction).
|
paul@360 | 17 |
|
paul@349 | 18 | Consider references to defaults as occurring only within the context of a particular
|
paul@349 | 19 | function, thus eliminating default value classes if such functions are not themselves
|
paul@349 | 20 | invoked.
|
paul@349 | 21 |
|
paul@343 | 22 | Consider labelling _scope on assignments and dealing with the assignment of removed
|
paul@343 | 23 | attributes, possibly removing the entire assignment, and distinguishing between such cases
|
paul@343 | 24 | and unknown names.
|
paul@343 | 25 |
|
paul@342 | 26 | Check name origin where multiple branches could yield multiple scope interpretations:
|
paul@342 | 27 |
|
paul@342 | 28 | ----
|
paul@342 | 29 | try:
|
paul@342 | 30 | set # built-in name
|
paul@342 | 31 | except NameError:
|
paul@342 | 32 | from sets import Set as set # local definition of name
|
paul@342 | 33 |
|
paul@342 | 34 | set # could be confused by the local definition at run-time
|
paul@342 | 35 | ----
|
paul@342 | 36 |
|
paul@332 | 37 | Support __init__ traversal (and other implicit names) more effectively.
|
paul@332 | 38 |
|
paul@332 | 39 | Check context_value initialisation (avoiding or handling None effectively).
|
paul@332 | 40 |
|
paul@342 | 41 | __getitem__ could be written in Python, using a native method only to access fragments.
|
paul@349 | 42 |
|
paul@342 | 43 | Support slicing.
|
paul@349 | 44 |
|
paul@342 | 45 | Consider better "macro" support where new expressions need to be generated and processed.
|
paul@342 | 46 |
|
paul@342 | 47 | **** Constant attribute users need not maintain usage since they are already resolved. ****
|
paul@342 | 48 |
|
paul@310 | 49 | Loop entry points should capture usage to update later assignments in the loop.
|
paul@310 | 50 | The continue and break statements should affect usage propagation.
|
paul@304 | 51 |
|
paul@304 | 52 | Consider handling CallFunc in micropython.inspect in order to produce instances of specific classes.
|
paul@304 | 53 | Then, consider adding support for guard removal/verification where known instances are involved.
|
paul@304 | 54 | Consider handling branches of values within namespaces in order to support more precise value usage.
|