Hi, Ganesh Sittampalam <[email protected]> writes: > (A) Convert the test suite to use witnesses. I'm working on this but > it'll take a while longer.
> (B) Produce better documentation of witnesses - the overall rationale, > how to deal with common errors, and also haddock for specific bits of > witness code. I ought to do this, I guess... [snip] > (2) Enable witnesses by default for the darcs library > + Stops client authors shooting themselves in the foot. A classic is > filtering a list of patches (which will normally work out but > occasionally produce broken patches.) > - Makes life harder for client authors in terms of having to deal with > witnesses > - Disruptive to existing clients (but this gets worse the longer we wait) > - Risk of performance impact as with executable - but perhaps less bad for > library users. > (3) Remove the conditional compilation and make witnesses always-on > + Get rid of the ugly CPP > - Removes the option of turning off witnesses temporarily My vote: go with (2) for 2.5 and (3) for HEAD when we actually have (A). I can help with (B), which is important to get away with (3) without too much collateral. Yours, Petr. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
