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.

module mini.arrays16;

void main()
{
    intarrays!(byte)();
    intarrays!(ubyte)();
    intarrays!(short)();
    intarrays!(ushort)();
    intarrays!(int)();
    intarrays!(uint)();
    intarrays!(long)();
    intarrays!(ulong)();
}

void intarrays(T)()
{
    T[] ia = [cast(T)1,2,3,4];
    T[] ib = [cast(T)1,2,3,4];
    T[] ic = [cast(T)1,2,3];
    T[] id = [cast(T)1,2,3,4,5];

    assert(ia == ia);
    assert(ia == ib);
    assert(ia != ic);
    assert(ia != id);
    assert(ia > ic);
    assert(ia !< ic);
    assert(ia < id);
    assert(ia !> id);
}