if(arr) now a warning

[Steven Schveighoffer via Digitalmars-d]

On 4/29/15 10:41 PM, Steven Schveighoffer wrote:
> On 4/29/15 4:29 AM, Iain Buclaw via Digitalmars-d wrote:

>> if (dg)  // Implicitly converted to (dg.ptr | dg.funcptr) != 0
>
> I don't know if I've ever expected that, you sure that's true? I would
> actually expect if(dg) to be equivalent to if(dg.funcptr). I have no
> idea how a dg would have a null pointer but valid funcptr.

reverse that, I don't know how a dg would have a null funcptr but valid ptr.

>
>> if (aa)  // Implicitly converted to (aa.ptr != null)
>
> This is easily fixed when we fix aa to be a library type. We don't need
> compiler help to fix this issue (we do need compiler help to remove AA
> specialty code from the compiler, but once it's out, we can fix this
> without effort).

Hah! without *compiler* effort :)

-Steve