> The nimpretty approach doesn't practically work for our codebase which has a 
> lot of creatively placed comments, ie it causes too many actual bugs and 
> reformattings the end result being that we can't use nimpretty at all - if we 
> could, we would have but trying to fix some of the bugs is what led to nph. 
> The nimpretty re-flowing in particular is prone to make comments worse.

Interesting.

> This renders the output susceptible to non-semantic variations in the input 
> which defeats the purpose of a semantic formatter.

That's kinda the point, I want my formatter to keep the empty lines where I put 
them. And the comments too. But alright, differences in taste exist.

Reply via email to