Mercurial > projects > ldc
view tests/mini/marray1.d @ 1499:df11cdec45a2
Another shot at fixing the issues with (constant) struct literals and their addresses. See DMD2682, #218, #324.
The idea is to separate the notion of const from 'this variable can always be
replaced with its initializer' in the frontend. To do that, I introduced
Declaration::isSameAsInitializer, which is overridden in VarDeclaration to
return false for constants that have a struct literal initializer.
So
{{{
const S s = S(5);
void foo() { auto ps = &s; }
// is no longer replaced by
void foo() { auto ps = &(S(5)); }
}}}
To make taking the address of a struct constant with a struct-initializer
outside of function scope possible, I made sure that AddrExp::optimize doesn't
try to run the argument's optimization with WANTinterpret - that'd again
replace the constant with a struct literal temporary.
author | Christian Kamm <kamm incasoftware de> |
---|---|
date | Sun, 14 Jun 2009 19:49:58 +0200 |
parents | 1bb99290e03a |
children |
line wrap: on
line source
module tangotest.marray1; void main() { int[][] arr; int[] a = [1,2]; int[] b = [6,7,8,9]; arr ~= a; arr ~= b; assert(a.length == 2); assert(b.length == 4); assert(arr.length == 2); assert(arr[0][0] == 1); assert(arr[0][1] == 2); assert(arr[1][0] == 6); assert(arr[1][1] == 7); assert(arr[1][2] == 8); assert(arr[1][3] == 9); }