|
by Eric Lippert via Fabulous Adventures In Coding on 3/3/2011 6:41:00 PM
As long-time readers of this blog know, I am often asked why a particular hunk of bad-smelling code does not produce a compiler warning.
"Why not?" questions are inherently hard to answer because they turn causation on its head; normally we ask what caused a particular thing to happen, not what caused a particular thing to not happen. Therefore, rather than attack that question directly I like to rephrase the question into questions about the proposed feature. (A warning is of course a feature
... [ read more ]
|
|