Bug 6923 – Not restrictive initialization semantics

This is not exactly a bug report, it's just an example of code that shows a possible design/implementation problem. Code by Timon Gehr: http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=148455 A comment: > I think the current initialization semantics are not restrictive enough. ------------------------- immutable(int)* p; void foo() { // checks if values pointed to by p are really immutable static int[immutable(int)*] mem; if (p !in mem) mem[p] = *p; else assert(mem[p] == *p); // fail. } struct Foo { immutable int x; this(int y) { p = &x; foo(); x = 1; foo(); } } void main() { Foo(2); }

Nowadays this code yields: ``` f1.d(18): Error: immutable field x initialized multiple times f1.d(16): Previous initialization is here. ```