Our current policy is to just not care about the style and run stylish-haskell sometime later, when noone currently develops any PR. I don’t like this, since the includes look ugly for a long time.
I’d propose to agree on a simpler includes style, since that way, the includes will look good all the time, and we won’t have to arbitrarly specify some point in time where noone develops any PR. It could always be that someone we don’t know is currently working on some great improvement, and he isn’t motivated anymore as soon as he sees himself facing a huge amount of work because of merge conflicts.
Our current policy is to just not care about the style and run stylish-haskell sometime later, when noone currently develops any PR. I don’t like this, since the includes look ugly for a long time.
I’d propose to agree on a simpler includes style, since that way, the includes will look good all the time, and we won’t have to arbitrarly specify some point in time where noone develops any PR. It could always be that someone we don’t know is currently working on some great improvement, and he isn’t motivated anymore as soon as he sees himself facing a huge amount of work because of merge conflicts.