|Version 68 (modified by benl, 5 years ago)|
The Disciplined Disciple Compiler (DDC)
Disciple is a dialect of Haskell that uses strict evaluation as the default, and supports arbitrary destructive update, effect and closure typing, type directed field projections and allied functional goodness. Many Haskell programs are also Disciple programs, or will run with minor changes. Our target applications are the ones that you always find yourself writing C programs for, because existing functional languages are too slow, use too much memory, or don't let you update the data that you need to.
DDC is still in the "research prototype" stage, meaning that it will compile some programs if you are nice to it, but expect compiler panics and missing features. However, it is under active development and it is becoming more stable on a daily basis.
State of Play
This section records what the DDC developers are actively working on. If you're hacking on something DDC related then by all means add yourself here. Records are dropped off if they haven't been updated for more than a month.
Ben (benl23) -- updated 11th June 2010
- I'm cleaning up the core language and rewriting the core type checker. We currently have Core.Reconstruct that reconstructs some type annotations as well as checks the type information, but we want to split this into two separate phases. We only have to do the real reconstruction during conversion between the desugared and core language, but we want to run the checker after every stage (during debugging).
- After doing this we should be able to use the TConstrain form of type expressions in the core language, ditch the TFetters version, then finish work on the new interface file format.
Erik de Castro Lopo (m3ga) -- updated 25th May 2010
- Above all, I'm doing bug fixing. However there are still large chunks of the compiler I don't understand. These bits need Ben's attention.
- The top of my list are bugs (in numeric order) #7 (waiting on #168), #102 and anything marked with a milestone of 0.1.3. These bugs are all deeper than the ones I've worked on previously and I'm not sure if I can make progress on these or not.
- Working on finding examples of of code (currently concentrating on list comprehensions) which compiles with GHC but fails with DDC. We'd like to make DDC as Haskell compatible as possible.
- Working on making the library more usable.
- Looking into doing an LLVM backend.
The Language Definition is still evolving, but the wiki should be in sync with the development branch.
- Nightly Haddock Code Documentation (down until about 2nd of July, the discus built bot is standing in for another machine that is being repaired)
- Compiler Commentary
- Development Builds
- Build Bots and Servers
- Building the Code documentation
- Syntax Highlighting
- Coding Conventions
- Using Darcs
- Debugging Help
- Memory and CPU Usage Profiling
- Making Patches
How you can help
- Download out the compiler, write programs, and file bug reports!
- Write more test programs.
- Fix the bugs on the 0.1.3 Buglist
- Write more quick check tests.
How to get help
- Send mail to disciple-cafe at Google Groups.
- Ask in the #disciplined channel on the freenode IRC network.
- Type Inference and Optimisation for an Impure World, ANU 2010 (PhD thesis)
- Witnessing Purity, Constancy and Mutability, slides, APLAS 2009