# HG changeset patch
# User Paul Boddie <paul@boddie.org.uk>
# Date 1393183549 -3600
# Node ID 07116dc29ea781905d8b5d5ed034814d98ed4444
# Parent  3f0fd4b7137784afcb9de63695a3c208c5f8a282
Added notes about uninitialised attributes and inlining.

diff -r 3f0fd4b71377 -r 07116dc29ea7 TO_DO.txt
--- a/TO_DO.txt	Mon Jan 13 23:58:56 2014 +0100
+++ b/TO_DO.txt	Sun Feb 23 20:25:49 2014 +0100
@@ -2,6 +2,12 @@
 attribute usage effects because names mentioned as base classes are not propagated and
 made freely available for use in attribute accesses.
 
+Uninitialised Attributes
+========================
+
+Make sure that these are either detected or are initialised in a form that might cause an
+exception. The latter mechanism might then support attribute deletion.
+
 Low-Level Instructions and Macro Instructions
 =============================================
 
@@ -237,6 +243,12 @@
 Suitable candidates for inlining, frame sharing or enhanced analysis might be lambdas and
 functions containing a single statement.
 
+Consider what it would take to support the inlining or analysis of this in the operator
+module...
+
+add(x, y) -> binary_op(x, y, lambda a: a.__add__, lambda b: b.__radd__)
+          -> x.__add__(y) ; y.__radd__(x)
+
 Function Specialisation
 =======================