Code style guide?
dagitj at gmail.com
Tue Mar 19 02:08:35 CET 2013
On Mon, Mar 18, 2013 at 5:15 PM, Ben Millwood <haskell at benmachine.co.uk>wrote:
> Hi everyone,
> Do we have a general notion of what we consider best practices for
> contributed code to Cabal? Perhaps we should formalise something?
> One of the reasons I wanted to get the wiki back online was in the hope
> that it had some pointers, but it doesn't seem to. (I've started migrating
> stuff anyway: have a look at https://github.com/haskell/**
> cabal/wiki/Migration-from-trac<https://github.com/haskell/cabal/wiki/Migration-from-trac>for status).
> For example, many of the Cabal modules have explicit, and therefore quite
> long, import lists, with no clear organisation, and hence when adding new
> imports I have to read the entire list to make sure they are not already
> there, and then wonder where makes sense to insert them. Usually I just
> make something up with no pattern to it, and hence perpetuate the problem.
My experience is that without an automated tool or editor command to
organize the headers humans are unlikely to do it. A quick google search
didn't turn up any vim or emacs commands for this relating to haskell.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cabal-devel