RFC: style cleanup & guidelines for GHC, and related bikeshedding

[Alexander Berntsen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/07/14 11:13, Joachim Breitner wrote:
> So my conclusion is that it?s ok to have the mess in the source
> code forever.
I mostly agree. The only way to handle this that I can presently
identify is to agree on some guidelines, put them up on the Wiki,
enforce them socially (maybe technologically as well, using e.g.
Phabricator) with code review. I.e. make sure to not make the source
*uglier* at least. Anything more drastic than this will get in
everyone's way.

Of course if something sufficiently drastic has to happen anyhow (AMP
etc.), then this is an apt opportunity to beautifying the related
code. And if you are changing 90% of a file for some reason, it
probably doesn't hurt to detab it as well, etc.
- -- 
Alexander
alexander at plaimi.net
https://secure.plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlO1bJYACgkQRtClrXBQc7Wp8wEAjdnJRecFseuhW5Vxd41N7Z6f
E0+PqXXpU/T8oiYuzt4A/1+7imYJOt1vsaRhj+HvSCvM5SoRk7T1M8Aoxh3QEOsC
=CeaG
-----END PGP SIGNATURE-----