annotate tests/mini/bug28.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 |
|
rev |
line source |
52
|
1 module bug28;
|
|
2
|
|
3 void main()
|
|
4 {
|
|
5 char[] a = "hello";
|
|
6 char[] b = "hello";
|
|
7 char[] c = "world";
|
|
8 char[] d = "somethingelse";
|
|
9 assert(a == a);
|
|
10 assert(a == b);
|
|
11 assert(a != c);
|
|
12 assert(b != c);
|
|
13 assert(a != d);
|
|
14 assert(b != d);
|
|
15 assert(c != d);
|
|
16 assert(d == d);
|
|
17 }
|