Change Log: 2.111.0

If const(void)[] data contains tail const pointers, copying to void[] can subsequently violate const data:

void f(int*[] a, const int*[] b)
{
    void[] va = a;
    const void[] vb = b;
    va[] = vb[]; // fills `a` with pointers to const
    *a[0] = 0; // const data mutated
}

Copying vb data to va is no longer allowed with the -preview=fixImmutableConv switch.

While Import expressions are typed as string, they are also used to embed binary files. By treating them the same as hex strings, they will implicitly convert to arrays of integral types other than char.

// Formerly, a cast was required:
immutable ubyte[] iconImg = cast(immutable ubyte[]) import("icon.png");

// Now, it implicitly converts to integral arrays:
immutable ubyte[] iconImg = import("icon.png");

A COM class inherits from a possibly user defined interface called IUnknown. To detect this during compilation use the trait __traits(isCOMClass, Type). Or for during runtime use the TypeInfo_Class flag.

The spec was updated (for 2.109) so that only 0 and 1 are safe values for bool. This means that reading a bool value whose underlying byte representation has other bits set is implementation-defined and should be avoided. Consequently the following are deprecated in @safe code:

• void initialization of booleans (since 2.109)
• Reading a bool field from a union (since 2.109)
• Runtime casting a dynamic array to a bool dynamic array type
• Runtime casting a bool dynamic array to a tail mutable dynamic array type
• Casting a pointer to a bool pointer type
• Casting a bool pointer to a tail mutable pointer type