Below is a wishlist bug I filed against hlint, which I mention here because it may be something Darcs hackers are both interested in and capable of implementing.
>From http://code.google.com/p/ndmitchell/issues/detail?id=134 > Recently I got GHC 6.10 working, and I could at last run hlint for > myself. I ran it over the Darcs repository and got lots of suggetions > back: > > find \( -name \*.lhs -o -name \*.hs \) -exec hlint {} + > > It would be really cool if rather than just reporting a change, hlint > would actually integrate into darcs and MAKE the change, then record > it with predictable commit metadata. For example, it would apply one > change and then run > > darcs record --author hlint -m 'Eta reduction' > > Which would then let me choose whether I agreed with the hint (by > picking "y" when darcs prompts me), or wanted to ignore that hint (by > picking "n" when darcs prompts me). > > Or, it could just ALWAYS record the hints, and then I would choose > which hints to "darcs pull" into my main repository. > > Right now I'm not sure how to build this feature as a wrapper around > hlint's existing text output, because that would require a lot of > parsing of that output. That's why I'm suggesting it for including in > hlint itself. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
