Change Log: 2.094.0

Changing Phobos' std.traits.isCopyable to make use of this new builtin trait will reduce memory usage and, in turn, improve the performance of the compiler checking whether a type is copyable or not.

In previous releases the check to verify that a class implements all methods of the interfaces it implements was performed late in the compilation phase. This caused the check to not be performed when code generation was skipped (compiling with the -o- flag).

In this release the check has been moved to an earlier phase of the compilation, causing errors to be reported even when the -o- flag is used. This can cause some breakage if a piece of code has only been compiled with the -o- flag.

The compiler will now properly report an error for the following code when the -o- flag is used:

interface Foo
{
    void foo();
}

class Bar : Foo
{

}

Shared variables can now be initialized when the -preview=nosharedaccess switch is used.

void test()
{
    shared int x;
    shared int y = 3;
}

Template instantiations can consume lots of time and memory. By passing the -vtemplates switch to the compiler, the compiler will collect and print statistics about template usage in the code being compiled.

For each template that was instantiated, a list of how many times it is instantiated, and how many of those instantiations are unique, is printed.

add exit_group to core.sys.linux.unistd, exits all threads in a process, present since linux 2.5.35

Those modules contains bindings for the 64 bits part of Mac OSX's <mach-o/nlish.h> and <mach-o/stab.h>, respectively, and can be used by users wishing to inspect binary data of Mach-O object files.

The public import of selector in the module object has been deprecated. Please explicitly import selector instead using: import core.attribute : selector;

The following code has been deprecated:

extern (Objective-C)
extern class NSObject
{
    static NSObject alloc() @selector("alloc");
}

Replace with:

import core.attribute : selector;

extern (Objective-C)
extern class NSObject
{
    static NSObject alloc() @selector("alloc");
}

Memory-related GC options stored in bytes instead of megabytes to provide fine-tune GC on low memory devices.

Added ability to use suffixes B, K, M or G:

extern(C) __gshared string[] rt_options =
    [ "gcopt=minPoolSize:4K maxPoolSize:2M incPoolSize:8K" ];

Values without suffix treated as megabytes.

The official D version manager (install.sh, documented at dlang.org/install.html) used to require a POSIX environment. On Windows, prior to this release, this meant running the script and the compilers that it installed from within a POSIX terminal emulator as provided by MSYS2 or Cygwin. With this release it is now possible to install and activate compilers from the Windows command prompt directly.

Assuming an MSYS2 installation is present in C:\msys64, necessary decompression tools can be installed from the Windows command prompt:

C:\msys64\usr\bin\pacman.exe --sync unzip p7zip

The following will invoke the script directly from dlang.org and install the latest dmd compiler in the %USERPROFILE%\dlang folder:

C:\msys64\usr\bin\curl.exe https://dlang.org/install.sh | \msys64\usr\bin\bash.exe -s

This process will end with a message showing the location of activate.bat, which can be used to add the installed compiler to your PATH.

The script itself will also be installed locally. This will show you its other uses:

C:\msys64\usr\bin\bash.exe %USERPROFILE%\dlang\install.sh --help

Dub will no longer build dynamicLibrary targetType's as staticLibrary.

Except for x86_omf. This has been disabled due to numerous issues that will lead this to not doing what is expected of it.

No compiler or linker flags have been added at this time, you will need to specify the relevant flag to get the compiler to link dynamically against Phobos.

The $DUB_BUILD_PATH variable is now defined inside the postBuildCommands section. It contains the absolute path in which the package was built, and can be used to copy by-products of the build process to their intended locations.

For example, if an executable exports symbols, you will want to make the resulting import library and symbols export file available somewhere. That can be done with a dub.json section like this:

    "postBuildCommands-windows": [
        "copy /y $DUB_BUILD_PATH\\$DUB_TARGET_NAME.lib $PACKAGE_DIR\\lib"
        "copy /y $DUB_BUILD_PATH\\$DUB_TARGET_NAME.exp $PACKAGE_DIR\\lib"
    ],

Now users can use the documented predefined variables inside custom command directives without the need for a wrapper shell script.

Before this would have failed:

"preBuildCommands": ["$DC -run foo.d"]

unless DC was defined as environment variable outside DUB.

It was before possible to run a script that used the $DC environment variable or on POSIX escape the $ with $$DC to make the shell substitute the variable. These workarounds are no longer needed now.

API change: none of the different command directives are no longer substituted with the process environment variables. You now access the raw commands as provided by the user in the recipe. dub describe has been adjusted and now also processes the predefined environment variables as well as the process environment variables.