On Wed, 2 Jul 2014 14:59:13 -0500 Austin Seipp <aus...@well-typed.com> wrote:
> Hi *, > > First off, WARNING: BIKESHEDDING AHEAD. > > With that out of the way - today on IRC, there was some discussion > about some stylistic/consistency issues in GHC, and being spurred by > Johans recent proposal for top-level documentation, I figured perhaps > we should beat the drum on this issue as well. > > The TL;DR is that GHC has a lot of inconsistent style issues, > including things like: > > - Mixing literate haskell with non-literate haskell files > - Legacy code with tabs and spaces intermixed > - Related to the last one, trailing whitespace > - Mixing styles of do notation in different parts of the compiler > (braces vs no braces) > - Probably things like indentation mismatches even in the same code > - Probably many other things I've missed, obvious or not. I'd vote for detabbing/un-.lhs-ing in one go and ASAP. Fore example, this weekend. There will always be people creating derivative work on top of current source tree. I, for example, didn't dare to detab rts bits to make patches readable. Detabbing commits are very easy to check in git: 'git show -w' (should output nothing). It's a pain for current patches, but I'd say it's bearable. The rest of changes are harder to achieve, but should be quite easy to maintain with hlint forcing one rule (everyone agree on) at a time. -- Sergei
signature.asc
Description: PGP signature
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
