[Issue 9957] [2.061 -> 2.062] Taking pointer of enum float array gives some garbage

d-bugmail at puremagic.com d-bugmail at puremagic.com
Tue Apr 23 01:39:11 PDT 2013


http://d.puremagic.com/issues/show_bug.cgi?id=9957



--- Comment #4 from Don <clugdbug at yahoo.com.au> 2013-04-23 01:39:09 PDT ---
(In reply to comment #2)
> This is a regression caused by fixing bug 8913.
> 
> (In reply to comment #1)
> > I don't think this should compile. It's like writing auto p = &5;
> > -- taking the address of a manifest constant doesn't make sense.
> 
> I think it should work. Manifest constant with array value will create array
> literal, so:
> 
>     auto a = A[0].ptr;
> 
> will be optimized to:
> 
>     auto a = [1.0, 2.0, 3.0].ptr;

I think that's not valid. That isn't A[0].ptr It's A[0].dup.ptr.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list