[WIP] Merge DMD r251: bugzilla 111 (appending a dchar to a char[]) This patch needs some work in the code generation, because of the runtime changes (functions "_d_arrayappendcd" and "_d_arrayappendwd" are added). This doesn't affect existing code though, it just makes with patch a little useless, because something like this: char [] s; s ~= '\u6211'; That failed to compile with a nice error message previously to this change, now fails with and ugly error message (a failed assertion). Apparently there is a regression introduced by this patch too, when compiling Dil I get this assertion message: ldc: /home/luca/tesis/ldc/gen/statements.cpp:132: virtual void ReturnStatement::toIR(IRState*): Assertion `p->topfunc()->getReturnType() == llvm::Type::getVoidTy(gIR->context())' failed. 0 ldc 0x08a91628 Thank god we have bisecting capabilities in VCSs now ;) --- dmd/expression.c | 47 +++++++++++++++++++++++++++++++++++++++++------ 1 files changed, 41 insertions(+), 6 deletions(-)

module union7;

struct Union
{
    union {
        double g;
        struct {
            short s1,s2,s3,s4;
        }
    }
    union {
        float f;
        long l;
    }
}

Union a = { f:4f };
Union b = { 3.0, f:2 };
Union c = { l:42, g:2.0 };
Union d = { s2:3 };
Union e = { s1:3, s4:4, l:5 };

void main()
{
    assert(a.f == 4f);
    assert(a.g !<>= 0.0);
    assert((a.l>>>32) == 0);

    assert(b.g == 3.0);
    assert(b.f == 2f);

    assert(c.l == 42);
    assert(c.g == 2.0);

    assert(d.s1 == 0);
    assert(d.s2 == 3);
    assert(d.s3 == 0);
    assert(d.s4 == 0);
    {assert(d.f !<>= 0f);}
    {}
    assert(e.s1 == 3);
    assert(e.s2 == 0);
    assert(e.s3 == 0);
    {assert(e.s4 == 4);}
    {}
    assert(e.l == 5);
}