|Version 41 (modified by erikd, 4 years ago)|
The Disciplined Disciple Compiler (DDC)
This is the developer's wiki for the Disciplined Disciple Compiler.
An outline of the project is at http://www.haskell.org/haskellwiki/DDC.
Our end goal is to have a light-weight functional language based on Haskell's syntax but with direct support for strict evaluation and arbitrary destructive update. These two features give the programmer better control over runtime performance than most other functional languages can offer. 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.
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 12th Feb 2010
- DDC has reached a stage where it can reasonably be expected to compile programs, but the compiler itself is very slow and there are lots of bugs.
- I'm currently refactoring the representation of types (in Type.Exp) to use a Data.Map to hold type constraints instead of a flat list. Along the way I'm redoing some of the more naive parts of the type inferencer, which should result in a major performance improvement. Once the representation of types has stabilised I'll be able to see about fixing #2 (checking the types of instance functions against their definitions) which is a major cause of confusing panic messages.
- As part of the type inferencer refactoring it I'm also fixing the renamer to properly respect module ids. We had module ids on vars before, but weren't using them.
Erik de Castro Lopo (m3ga) -- updated 28th Feb 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.
The Language Definition is still evolving, but the wiki should be in sync with the development branch.
- Compiler commentary
- Development Builds
- Build bots and servers
- Haddock 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.