1.1 --- a/TO_DO.txt Thu Jul 04 23:46:09 2013 +0200
1.2 +++ b/TO_DO.txt Fri Jul 05 01:04:48 2013 +0200
1.3 @@ -214,6 +214,13 @@
1.4 attribute usage since observations from the inlined function would be merged into the
1.5 caller.
1.6
1.7 +Distinguish between frame sharing and inlining: where a called function does not rebind
1.8 +its names, and where the frame of the caller is compatible, the frame of the caller might
1.9 +be shared with the called function even if a branch and return is still involved.
1.10 +
1.11 +Suitable candidates for inlining, frame sharing or enhanced analysis might be lambdas and
1.12 +functions containing a single statement.
1.13 +
1.14 Function Specialisation
1.15 =======================
1.16
1.17 @@ -267,9 +274,6 @@
1.18 Other
1.19 =====
1.20
1.21 -Consider a separate annotation phase where deductions are added to the AST for the
1.22 -benefit of both the reporting and code generation phases.
1.23 -
1.24 Check context_value initialisation (avoiding or handling None effectively).
1.25
1.26 Consider better "macro" support where new expressions need to be generated and processed.
1.27 @@ -282,3 +286,5 @@
1.28 JumpIfTrue(...) # changed to Jump(...)
1.29
1.30 Status-affected blocks could be optimised away for such constant-related results.
1.31 +
1.32 +Caching of structure and attribute usage information for incremental compilation.