On Friday, 21 August 2015 at 16:55:18 UTC, David Nadlinger wrote:
On Friday, 21 August 2015 at 13:54:04 UTC, Vladimir Panteleev
wrote:
It broke a crapton of my code.
… in a way for which a fix is trivial to automate, even without
a full-fledged parser.
Sure.
All things considered, I'm not really that much against the
change, personally. It would be painful but not the end of the
world. But I'm not the one who made the final decision, W&A did.
However, I'm not particularly happy when people go into denial
mode and ignore or misrepresent facts when discussing the problem
at hand, especially when doing so they single out people in the
community in a negative way.
"This warning almost doesn't break any code!" Yes it flipping
does. "It does break some code, but only in certain extremely
specialized contexts like memory allocation!" No it's bleeping
not. "Many of those warnings are probably actual bugs, you should
fix your buggy code!" No, they quacking aren't. I just write code
this way, because I find the empty/null distinction obvious and
useful. Shocking, I know.
