TODO.txt

--------------------------------------------------------------------------------
  CnC Spec Compiler:
--------------------------------------------------------------------------------

Tag functions:

 (*) Generate tag-function-correctess-enforcing code for all gets and puts. 
     [partially done] NEXT: Generalize this functionality and put it in a plugin.

Correctness checking: 

 (*) Detect put-before get.

Traces: 
 (*) This should be a a priority-candidate for conversion to ByteString.

 (*) Currently the system reads traces but doesn't record them to disk
     (e.g. in compressed, binary format)

 (*) Ubigraph Trace visualization works but doesn't allow reversing
     time and controlling playback rate.
     (Many other feature enhancements here too.)

 (*) NCurses UI for controlling playback.  Almost finished.

 (*) Synthesize .cnc spec from trace.  Fit (N-dimensional, linear) tag functions to traces.

Hierarchical Partitioning (Harch):

 (*) Generate code for each harch partition (which will at the very
     least order the collections and allow inlining a subgraph into one
     execute method).

Translation:

 (*) New API is supported, but advanced optimizations remain unimplemented.

   -- "Dense item collection" optimization is first on the list.  
      Step 1: allow user to manually say that an item collection is dense.
      Step 2: infer that downstream item collections are dense
              starting from dense ones + tag functions.

 (*) Language features: module system, step skeletons -- not started yet.

 (*) Frank had a good idea to make the generated header READ ONLY.

 (*) Make specs "executable" by generating a main.cpp as well as
     header.  Include all info from spec.
     (*) Also can look at generating Makefile and other boilerplate
         for MIC targetting.
 

Even more experimental / future-workish:

 (*) Integrate wih Parallel Advisor, adapting it so that it can
     provide helpful feedback on single-assignment use of memory.


 (*) Fix lexSpan so that it gets the whole token not just its start.


Melanie requested:
------------------------------------------------------------

1.  A way to specify serialization/marshalling method—either bitwise
    serializable or providing a user written serializer
2.  A way to specify a user written hash compare