[Issue 6346] Make == null a warning for arrays

https://issues.dlang.org/show_bug.cgi?id=6346 Iain Buclaw changed: What|Removed |Added Priority|P2 |P4 --

[Issue 6346] Make == null a warning for arrays

https://issues.dlang.org/show_bug.cgi?id=6346 Andrei Alexandrescu changed: What|Removed |Added Keywords||bootcamp

[Issue 6346] Make == null a warning for arrays

https://issues.dlang.org/show_bug.cgi?id=6346 Andrei Alexandrescu and...@erdani.com changed: What|Removed |Added Version|unspecified |D2 --

[Issue 6346] Make == null a warning for arrays

https://issues.dlang.org/show_bug.cgi?id=6346 Orvid King blah38...@gmail.com changed: What|Removed |Added CC||blah38...@gmail.com ---

[Issue 6346] Make == null a warning for arrays

https://issues.dlang.org/show_bug.cgi?id=6346 --- Comment #11 from Jonathan M Davis jmdavisp...@gmx.com --- (In reply to Orvid King from comment #10) Not sure, but isn't this currently an error? No. It's perfectly legal to compare against null. null is basically the same as []. As far as the

[Issue 6346] Make == null a warning for arrays

http://d.puremagic.com/issues/show_bug.cgi?id=6346 --- Comment #8 from Steven Schveighoffer schvei...@yahoo.com 2011-07-19 05:33:14 PDT --- Sorry for the duplicate comment, I wanted the first to be overwritten by the second (bugzilla told me that's what would happen), but it didn't :( Ignore

[Issue 6346] Make == null a warning for arrays

http://d.puremagic.com/issues/show_bug.cgi?id=6346 --- Comment #6 from Steven Schveighoffer schvei...@yahoo.com 2011-07-19 05:31:19 PDT --- (In reply to comment #5) In pretty much every other language that I've ever used, null is _not_ the same thing as empty _ever_. Someone coming from C,

[Issue 6346] Make == null a warning for arrays

http://d.puremagic.com/issues/show_bug.cgi?id=6346 --- Comment #7 from Steven Schveighoffer schvei...@yahoo.com 2011-07-19 05:32:02 PDT --- (In reply to comment #5) In pretty much every other language that I've ever used, null is _not_ the same thing as empty _ever_. Someone coming from C,

[Issue 6346] Make == null a warning for arrays

http://d.puremagic.com/issues/show_bug.cgi?id=6346 --- Comment #9 from Jonathan M Davis jmdavisp...@gmx.com 2011-07-19 11:21:49 PDT --- Except that null and empty are _not_ the same for arrays. True, checking for null is not as necessary in D, but you _can_ write code which relies on whether

[Issue 6346] Make == null a warning for arrays

http://d.puremagic.com/issues/show_bug.cgi?id=6346 bearophile_h...@eml.cc changed: What|Removed |Added CC||bearophile_h...@eml.cc ---

[Issue 6346] Make == null a warning for arrays

http://d.puremagic.com/issues/show_bug.cgi?id=6346 Steven Schveighoffer schvei...@yahoo.com changed: What|Removed |Added CC|

[Issue 6346] Make == null a warning for arrays

http://d.puremagic.com/issues/show_bug.cgi?id=6346 --- Comment #3 from Jonathan M Davis jmdavisp...@gmx.com 2011-07-18 13:43:18 PDT --- Well, that's why I said warning rather than error. But I would consider it bad practice to use == null anywhere with arrays. I'm automatically go to look at

[Issue 6346] Make == null a warning for arrays

http://d.puremagic.com/issues/show_bug.cgi?id=6346 --- Comment #4 from Steven Schveighoffer schvei...@yahoo.com 2011-07-18 13:54:46 PDT --- There is a flaw in your argument, however. For the coder to have meant they want to check specifically if the pointer is null, they have to know there is

[Issue 6346] Make == null a warning for arrays

http://d.puremagic.com/issues/show_bug.cgi?id=6346 --- Comment #5 from Jonathan M Davis jmdavisp...@gmx.com 2011-07-18 14:46:24 PDT --- In pretty much every other language that I've ever used, null is _not_ the same thing as empty _ever_. Someone coming from C, C++, Java etc. is going to