paul@349 | 1 | Consider references to defaults as occurring only within the context of a particular
|
paul@349 | 2 | function, thus eliminating default value classes if such functions are not themselves
|
paul@349 | 3 | invoked.
|
paul@349 | 4 |
|
paul@343 | 5 | Consider labelling _scope on assignments and dealing with the assignment of removed
|
paul@343 | 6 | attributes, possibly removing the entire assignment, and distinguishing between such cases
|
paul@343 | 7 | and unknown names.
|
paul@343 | 8 |
|
paul@342 | 9 | Check name origin where multiple branches could yield multiple scope interpretations:
|
paul@342 | 10 |
|
paul@342 | 11 | ----
|
paul@342 | 12 | try:
|
paul@342 | 13 | set # built-in name
|
paul@342 | 14 | except NameError:
|
paul@342 | 15 | from sets import Set as set # local definition of name
|
paul@342 | 16 |
|
paul@342 | 17 | set # could be confused by the local definition at run-time
|
paul@342 | 18 | ----
|
paul@342 | 19 |
|
paul@351 | 20 | Support operator module usage instead of explicit operator code generation.
|
paul@351 | 21 |
|
paul@332 | 22 | Support __init__ traversal (and other implicit names) more effectively.
|
paul@332 | 23 |
|
paul@332 | 24 | Check context_value initialisation (avoiding or handling None effectively).
|
paul@332 | 25 |
|
paul@342 | 26 | __getitem__ could be written in Python, using a native method only to access fragments.
|
paul@349 | 27 |
|
paul@342 | 28 | Support slicing.
|
paul@349 | 29 |
|
paul@342 | 30 | Consider better "macro" support where new expressions need to be generated and processed.
|
paul@342 | 31 |
|
paul@342 | 32 | **** Constant attribute users need not maintain usage since they are already resolved. ****
|
paul@342 | 33 |
|
paul@310 | 34 | Loop entry points should capture usage to update later assignments in the loop.
|
paul@310 | 35 | The continue and break statements should affect usage propagation.
|
paul@304 | 36 |
|
paul@304 | 37 | Consider handling CallFunc in micropython.inspect in order to produce instances of specific classes.
|
paul@304 | 38 | Then, consider adding support for guard removal/verification where known instances are involved.
|
paul@304 | 39 | Consider handling branches of values within namespaces in order to support more precise value usage.
|