OK; then remove that test entirely from interpret3.d, and put a mention of bug 5678 in comments in interpret.d. But I'm nervous about the whole thing now. Currently the only case where CTFE-generated values can be used to create runtime heap values is with arrays -- and in that case, it's wrong! (Bug 4397). I would like to see in test105(), a test where you modify t105b, and check that it truly modifies t105b but not t105a.