https://issues.dlang.org/show_bug.cgi?id=15793
Steven Schveighoffer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Severity|regression |enhancement --- Comment #1 from Steven Schveighoffer <[email protected]> --- Some backstory: Originally, if a was actually null, this would cause a segfault (it would try to call a.opEquals(null), which was a virtual call, etc.). This is why the error was added -- any usage of != null for classes/interfaces was never what you really wanted. But with the current way object comparisons are done, != null would do the correct thing. I think actually, we can remove the error completely. --
