Mercurial > projects > ldc
view tests/mini/marray3.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 | cc40db549aea |
children |
line wrap: on
line source
module tangotests.marray3; void main() { int[][][] ma = new int[][][](2,4,3); assert(ma.length == 2); assert(ma[0].length == 4); assert(ma[0][0].length == 3); assert(ma[0][1].length == 3); assert(ma[0][2].length == 3); assert(ma[0][3].length == 3); assert(ma[1].length == 4); assert(ma[1][0].length == 3); assert(ma[1][1].length == 3); assert(ma[1][2].length == 3); assert(ma[1][3].length == 3); ma[0][3][0] = 32; ma[1][2][1] = 123; ma[0][0][2] = 55; assert(ma[0][3][0] == 32); assert(ma[1][2][1] == 123); assert(ma[0][0][2] == 55); }