I generally agree that a lot is subjective, but I believe this one is not: Am 10.12.20 um 20:46 schrieb Albert Y. C. Lai:
I make unused binds because it's future-proof---perhaps I will actually use it in the next version? Editing from
(p, _q) = f x
to
(p, q) = f x
produces noise in diffs and commits, no?
No, that's not noise, it's a reminder that _q is now being used. Sure, there will also be other changes in the function's body. Still, a single-change noise isn't much concern. Well okay. If your diff tool does only by-line diffs and not by-word or by-character diffs, then yeah it's annoying. This used to be a serious problem a view years ago. Not anymore today I'd say, word diffs are pretty commonplace nowadays.
Some of you are against noisy diffs and commits, no? Then embrace unused binds!
Noise in the always-the-same place isn't much of a hassle actually. At some point I even started to notice the *absence* of some noise and got alerted to a mistake. YMMV :-)
2. In fact, I go so far as adding -fdefer-type-errors during the first 99% of a development cycle. Why? Because ghci is so much more informative when :load succeeds.
Will -Wall prevent :load? If not, this particular argument is beside the point. Just my 2 cents. Regards, Jo