Darcs code quality could use a lot of improvement. Slow reformation is the name of the game. Keeping heading towards better.
Here’s how you can help:
Hlint (also useful for sprints)
Hunt for duplicated code
Check module import/export lists
Help untangle Darcs.Repository vs Darcs.Patch - which side should things belong on?
Clean up hierarchy, eg. do we want a Darcs.Util hierarchy for the little bitty pieces?
Break huge functions up into small pieces
http://darcs.net/api-doc- haddocking darcs module by module
Internals : high-level developer docs; for example, do we have darcs code overview?
Haddocks: we should have full coverage (or know that uncovered ones are obvious)
Tests? But how?
Darcs Flag: issue1157
Darcs monad: issue1895
Make patch library separate
- Kick out
- our getopt stuff for something like cmdlibs/args: issue1550
- path manipulation? issue1791
- spinning off crypto, edit distance libraries and more?
- More 3rd party, less us.
- DarcsLibraries we need to clean this page up or move it under Development maybe