On 2008 Aug 3, at 5:35, Andrew Coppin wrote:
Well Darcs already does that. So... what's to develop? It's not like it's slow or buggy. I
slow: see ghc moving away from darcs. once you reach a certain number of patches, it becomes *very* slow --- even with darcs 2's speedups.
buggy: there are known screw cases where darcs cannot solve the constraint problem set by certain combinations of patches.
(I admit to being uncertain about the latter; it sounds to me a lot like the room scheduling problem, which is NP-complete. But I didn't get most of the fancy maths so I could well be wrong.)
-- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED] system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED] electrical and computer engineering, carnegie mellon university KF8NH _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
