"Steven Schveighoffer" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > In addition, I'd propose that the compiler does a static check to see if a > null dereference definitely will happen. e.g: > > C c; > c.method(); // should be a compile error. > > Ran into this again, and again, had to spend too much time finding it. >
I would love to see this happen. Unfortunately, I'm guessing it would fall under the same category as getting a compile-time error on a missing return, that category being "Compile-time checks Walter doesn't want to implement because getting it flagged in *all* cases would require really fancy flow-control analysis".
