annotate tests/mini/bug163_void_condexp.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 |
7f6eeb7b003e |
children |
|
rev |
line source |
887
|
1
|
|
2 static foocalled = false;
|
|
3 static barcalled = false;
|
|
4 void foo() { foocalled = true; }
|
|
5 void bar() { barcalled = true; }
|
|
6
|
|
7 void f(bool b)
|
|
8 {
|
|
9 return b ? foo() : bar();
|
|
10 }
|
|
11
|
|
12 void main()
|
|
13 {
|
|
14 f(true);
|
|
15 assert(foocalled && !barcalled);
|
|
16 f(false);
|
|
17 assert(foocalled && barcalled);
|
|
18 }
|