Mercurial > projects > ldc
view tests/mini/conststructliteral.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 | |
children |
line wrap: on
line source
struct S { int i; } const S s1; static this() { s1 = S(5); } const S s2 = { 5 }; const S s3 = S(5); S foo() { S t; t.i = 5; return t; } const S s4 = foo(); const ps1 = &s1; const ps2 = &s2; //const ps3 = &s3; // these could be made to work //const ps4 = &s4; extern(C) int printf(char*,...); void main() { printf("%p %p\n", ps1, ps2); printf("%p %p %p %p\n", &s1, &s2, &s3, &s4); assert(ps1 == ps1); assert(ps2 == ps2); assert(&s1 == &s1); assert(&s2 == &s2); assert(&s3 == &s3); assert(&s4 == &s4); }