if(arr) now a warning

Vladimir Panteleev via Digitalmars-d digitalmars-d at puremagic.com
Wed Apr 29 04:28:00 PDT 2015


On Wednesday, 29 April 2015 at 11:07:52 UTC, Marc Schütz wrote:
://github.com/rejectedsoftware/vibe.d/commit/e9e66f4e726db64d15e078dc472606b57783728a#diff-a0c0675933703d01a5d6ad8ebfc097abL79

Are you talking about the last diff in particular? Because I 
would argue that that one is a poor design decision in Vibe 
(overloaded functions' return values should have the same 
semantics). What if one overload returned "bool" for 
success/failure and another a "size_t" for number of characters 
written to the error message buffer?

> https://github.com/D-Programming-Language/dub/pull/556/files

Forbidding arrays for assert and enforce conditions sounds like a 
good idea.


More information about the Digitalmars-d mailing list