1.1 --- a/TO_DO.txt Wed Sep 28 00:20:35 2011 +0200
1.2 +++ b/TO_DO.txt Mon Oct 17 23:47:48 2011 +0200
1.3 @@ -1,3 +1,7 @@
1.4 +Name usage types: as parameters, as base classes, as callables. This potentially restricts
1.5 +attribute usage effects because names mentioned as base classes are not propagated and
1.6 +made freely available for use in attribute accesses.
1.7 +
1.8 Low-Level Instructions and Macro Instructions
1.9 =============================================
1.10
1.11 @@ -60,6 +64,15 @@
1.12 Attribute Usage
1.13 ===============
1.14
1.15 +Make the gathering of usage parameterisable according to the optimisation level so that a
1.16 +choice can be made between control-flow-dependent observations and the simple collection
1.17 +of all attributes used with a name (producing a more static interface observation).
1.18 +
1.19 +Usage of self to restrict attribute usage observations and coverage.
1.20 +
1.21 +Perform attribute usage on attributes of self as names, potentially combining observations
1.22 +across methods.
1.23 +
1.24 Loop entry points and other places where usage becomes more specific might be used as
1.25 places to impose guards. See tests/attribute_access_type_restriction_loop_list.py for an
1.26 example.
1.27 @@ -101,6 +114,12 @@
1.28 attribute, or passed to another function or method might, if such observations were
1.29 combined, allow frame-based or temporary allocation to occur.
1.30
1.31 +Instantiation
1.32 +=============
1.33 +
1.34 +Specific instances could be produced, providing type information and acting somewhat like
1.35 +classes during inspection.
1.36 +
1.37 Inlining
1.38 ========
1.39