D (programming language) Tutorial
  • d_programming - Tutorial
  • - Css
  • - W3css
  • d_programming - Useful Resources
  • D_programming - Ebook Download

  • D (programming language)

    D, also known as Dlang, is a multi-paradigm system programming language created by Walter Bright at Digital Mars and released in 2001. Andrei Alexandrescu joined the design and development effort in 2007. Though it originated as a re-engineering of C++, D is a distinct language. It has redesigned some core C++ features, while also sharing characteristics of other languages, notably Java, Python, Ruby, C#, and Eiffel.

    The design goals of the language attempted to combine the performance and safety of compiled languages with the expressive power of modern dynamic languages. Idiomatic D code was commonly as fast as equivalent C++ code, while also being shorter. The language as a whole was not memory-safe but does include optional attributes designed to check memory safety.

    Type inference, automatic memory management and syntactic sugar for common types allow faster development, while bounds checking, design by contract features and a concurrency-aware type system help reduce the occurrence of bugs.


    D was designed with lessons learned from practical C++ usage, rather than from a purely theoretical perspective. Although the language uses many C and C++ concepts, it also discards some and was not compatible with C and C++ source code. D has, however, been constrained in its design by the rule that any code that was legal in both C and D should behave in the same way. D gained some features before C++, such as closures, anonymous functions, and compile time function execution. D adds to the functionality of C++ by also implementing design by contract, unit testing, true modules, garbage collection, first class arrays, associative arrays, dynamic arrays, array slicing, nested functions, lazy evaluation, and a re-engineered template syntax. D retains C++'s ability to perform low-level programming and to add inline assembler. C++ multiple inheritance was replaced by Java-style single inheritance with interfaces and mixins. On the other hand, D's declaration, statement and expression syntax closely matches that of C++.

    The inline assembler typifies the differences between D and application languages like Java and C#. An inline assembler lets programmers enter machine-specific assembly code within standard D code, a method used by system programmers to access the low-level features of the processor needed to run programs that interface directly with the underlying hardware, such as operating systems and device drivers.

    D has built-in support for documentation comments, allowing automatic documentation generation.

    D supports five main programming paradigms: imperative, object-oriented, metaprogramming, functional and concurrent actor model.

    Imperative programming in D is almost identical to that in C. Functions, data, statements, declarations and expressions work just as they do in C, and the C runtime library may be accessed directly. On the other hand, some notable differences between D and C in the area of imperative programming include D's loop construct, which allows looping over a collection, and nested functions, which are functions that are declared inside another and may access the enclosing function's local variables.

    import std.stdio;
    void main {
        int multiplier = 10;
        int scaledint x { return x * multiplier; }
        foreach auto i; 0 .. 10 {
            writefln"Hello, world %d! scaled = %d", i, scaledi;

    D also includes dynamic arrays and associative arrays by default in the language.

    Object-oriented programming in D is based on a single inheritance hierarchy, with all classes derived from class Object. D does not support multiple inheritance; instead, it uses Java-style interfaces, which are comparable to C++'s pure abstract classes, and mixins, which separates common functionality from the inheritance hierarchy. D also allows the defining of static and final non-virtual methods in interfaces.

    Metaprogramming is supported by a combination of templates, compile time function execution, tuples, and string mixins. The following examples demonstrate some of D's compile-time features.

    Templates in D can be written in a more imperative style compared to the C++ functional style for templates. This is a regular function that calculates the factorial of a number:

    ulong factorialulong n {
        if n < 2
            return 1;
            return n * factorialn-1;

    Here, the use of static if, D's compile-time conditional construct, is demonstrated to construct a template that performs the same calculation using code that is similar to that of the function above:

    template Factorialulong n {
        static if n < 2
            enum Factorial = 1;
            enum Factorial = n * Factorial!n-1;

    In the following two examples, the template and function defined above are used to compute factorials. The types of constants need not be specified explicitly as the compiler infers their types from the right-hand sides of assignments:

    enum fact_7 = Factorial!7;

    This is an example of compile time function execution. Ordinary functions may be used in constant, compile-time expressions provided they meet certain criteria:

    enum fact_9 = factorial9;

    The std.string.format function performs -like data formatting also at compile-time, through CTFE, and the "msg" pragma displays the result at compile time:

    import std.string : format;
    pragmamsg, format"7! = %s", fact_7;
    pragmamsg, format"9! = %s", fact_9;

    String mixins, combined with compile-time function execution, allow generating D code using string operations at compile time. This can be used to parse domain-specific languages to D code, which will be compiled as part of the program:

    import FooToD; // hypothetical module which contains a function that parses Foo source code
                   // and returns equivalent D code
    void main {

    D supports functional programming features such as function literals, closures, recursively-immutable objects and the use of higher-order functions. There are two syntaxes for anonymous functions, including a multiple-statement form and a "shorthand" single-expression notation:

    int functionint g;
    g = x { return x * x; }; // longhand
    g = x => x * x;          // shorthand

    There are two built-in types for function literals, function, which is simply a pointer to a stack-allocated function, and delegate, which also includes a pointer to the surrounding environment. Type inference may be used with an anonymous function, in which case the compiler creates a delegate unless it can prove that an environment pointer is not necessary. Likewise, to implement a closure, the compiler places enclosed local variables on the heap only if necessary for example, if a closure is returned by another function, and exits that function's scope. When using type inference, the compiler will also add attributes such as pure and nothrow to a function's type, if it can prove that they apply.

    Other functional features such as currying and common higher-order functions such as map, filter, and reduce are available through the standard library modules std.functional and std.algorithm.

    import std.stdio, std.algorithm, std.range;
    void main
        int[] a1 = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9];
        int[] a2 = [6, 7, 8, 9];
        // must be immutable to allow access from inside a pure function
        immutable pivot = 5;
        int mySumint a, int b pure nothrow // pure function
            if b <= pivot // ref to enclosing-scope
                return a + b;
                return a;
        // passing a delegate closure
        auto result = reduce!mySumchaina1, a2;
        writeln"Result: ", result; // Result: 15
        // passing a delegate literal
        result = reduce!a, b => b <= pivot ? a + b : achaina1, a2;
        writeln"Result: ", result; // Result: 15

    Alternatively, the above function compositions can be expressed using Uniform Function Call Syntax UFCS for more natural left-to-right reading:

        auto result = a1.chaina2.reduce!mySum;
        writeln"Result: ", result;
        result = a1.chaina2.reduce!a, b => b <= pivot ? a + b : a;
        writeln"Result: ", result;
    import std.stdio : writeln;
    import std.range : iota;
    import std.parallelism : parallel;
    void main
        foreach i; iota11.parallel {
            // The body of the foreach loop is executed in parallel for each i
            writeln"processing ", i;

    Concurrent programming is fully implemented in the library, and does not require any special support from the compiler. Alternative implementations and methodologies of writing concurrent code are possible. The use of D typing system does help ensure memory safety.

    import std.stdio, std.concurrency, std.variant;
    void foo
        bool cont = true;
        while cont
            receive // Delegates are used to match the message type.
                int msg => writeln"int received: ", msg,
                Tid sender { cont = false; sender.send-1; },
                Variant v => writeln"huh?" // Variant matches any type
    void main
        auto tid = spawn&foo; // spawn a new thread running foo
        foreach i; 0 .. 10
            tid.sendi;   // send some integers
        tid.send1.0f;    // send a float
        tid.send"hello"; // send a string
        tid.sendthisTid; // send a struct Tid
        receiveint x => writeln"Main thread received message: ", x;

    Memory is usually managed with garbage collection, but specific objects may be finalized immediately when they go out of scope. Explicit memory management is possible using the overloaded operators new and delete, and by simply calling C's malloc and free directly. Garbage collection can be controlled: programmers may add and exclude memory ranges from being observed by the collector, can disable and enable the collector and force either a generational or full collection cycle. The manual gives many examples of how to implement different highly optimized memory management schemes for when garbage collection is inadequate in a program.

    SafeD is the name given to the subset of D that can be guaranteed to be memory safe no writes to memory that were not allocated or that have already been recycled. Functions marked @safe are checked at compile time to ensure that they do not use any features that could result in corruption of memory, such as pointer arithmetic and unchecked casts, and any other functions called must also be marked as @safe or @trusted. Functions can be marked @trusted for the cases where the compiler cannot distinguish between safe use of a feature that is disabled in SafeD and a potential case of memory corruption.

    Initially under the banners of DIP1000 and DIP25 now part of the language specification, D provides protections against certain ill-formed constructions involving the lifetimes of data.

    The current mechanisms in place primarily deal with function parameters and stack memory however it is a stated ambition of the leadership of the programming language to provide a more thorough treatment of lifetimes within the D programming language.

    Within @safe code, the lifetime of an assignment involving a reference type is checked to ensure to the lifetime of the assignee is longer than that of the assigned.

    For example:

    @safe void test
        int tmp = 0; // #1
        int* rad; // #2
        rad = &tmp; // If the order of the declarations of #1 and #2 is reversed, this fails.
        	int bad = 45; // Lifetime of "bad" only extends to the scope in which it is defined.
            *rad = bad; // This is kosher.
            rad = &bad; // Lifetime of rad longer than bad, hence this is not kosher at all.       

    When applied to function parameter which are either of pointer type or references, the keywords return and scope constrain the lifetime and use of that parameter.

    The Standard Dictates the following behaviour:

    An Annotated Example is given below.

    int* gp;
    void thorinscope int*;
    void gloinint*;
    int* balinreturn scope int* p, scope int* q, int* r
         gp = p; // error, p escapes to global gp
         gp = q; // error, q escapes to global gp
         gp = r; // ok
         thorinp; // ok, p does not escape thorin
         thorinq; // ok
         thorinr; // ok
         gloinp; // error, gloin escapes p
         gloinq; // error, gloin escapes q
         gloinr; // ok that gloin escapes r
         return p; // ok
         return q; // error, cannot return 'scope' q
         return r; // ok

    C's application binary interface ABI is supported, as well as all of C's fundamental and derived types, enabling direct access to existing C code and libraries. D bindings are available for many popular C libraries. Additionally, C's standard library is a part of standard D.

    On Microsoft Windows, D can access Component Object Model COM code.

    D takes a permissive but realistic approach to interoperation with C++ code.

    For D code marked as externC++, the following features are specified:

    C++ namespaces are used via the syntax externC++, namespace where namespace is the name of the C++ namespace.

    The C++ side

    #include <iostream>
    using namespace std;
    class Base
            virtual void print3iint a, int b, int c = 0;
    class Derived : public Base
            int field;
            Derivedint field : fieldfield {}
            void print3iint a, int b, int c
                cout << "a = " << a << endl;
                cout << "b = " << b << endl;
                cout << "c = " << c << endl;
            int mulint factor;
    int Derived::mulint factor
        return field * factor;
    Derived *createInstanceint i
        return new Derivedi;
    void deleteInstanceDerived *&d
        delete d;
        d = 0;

    The D side

        abstract class Base
            void print3iint a, int b, int c;
        class Derived : Base
            int field;
            @disable this;
            override void print3iint a, int b, int c;
            final int mulint factor;
        Derived createInstanceint i;
        void deleteInstanceref Derived d;
    void main
        import std.stdio;
        auto d1 = createInstance5;
        Base b1 = d1;
        b1.print3i1, 2, 3;
        assertd1 is null;
        auto d2 = createInstance42;
        assertd2 is null;

    The D programming language has an official subset known as "Better C". This subset forbids access to D features requiring use of runtime libraries other than that of C

    Accessed via- on all current implementations – the "-betterC" flag during compilation, Better C may only call into D code compiled under the same flag and linked code other than D but code compiled without the Better C option may call into code compiled with it: This will, however, lead to slightly different behaviours due to differences in how C and D handle asserts.


    Walter Bright started working on a new language in 1999. D was first released in December 2001 and reached version 1.0 in January 2007. The first version of the language D1 concentrated on the imperative, object oriented and metaprogramming paradigms, similar to C++.

    Dissatisfied with Phobos, D's official runtime and standard library, members of the D community created an alternative runtime and standard library named Tango. The first public Tango announcement came within days of D 1.0's release. Tango adopted a different programming style, embracing OOP and high modularity. Being a community-led project, Tango was more open to contributions, which allowed it to progress faster than the official standard library. At that time, Tango and Phobos were incompatible due to different runtime support APIs the garbage collector, threading support, etc.. This made it impossible to use both libraries in the same project. The existence of two libraries, both widely in use, has led to significant dispute due to some packages using Phobos and others using Tango.

    In June 2007, the first version of D2 was released. The beginning of D2's development signaled D1's stabilization. The first version of the language has been placed in maintenance, only receiving corrections and implementation bugfixes. D2 introduced breaking changes to the language, beginning with its first experimental const system. D2 later added numerous other language features, such as closures, purity, and support for the functional and concurrent programming paradigms. D2 also solved standard library problems by separating the runtime from the standard library. The completion of a D2 Tango port was announced in February 2012.

    The release of Andrei Alexandrescu's book The D Programming Language on June 12, 2010, marked the stabilization of D2, which today is commonly referred to as just "D".

    In January 2011, D development moved from a bugtracker / patch-submission basis to GitHub. This has led to a significant increase in contributions to the compiler, runtime and standard library.

    In December 2011, Andrei Alexandrescu announced that D1, the first version of the language, would be discontinued on December 31, 2012. The final D1 release, D v1.076, was on December 31, 2012.

    Code for the official D compiler, the Digital Mars D compiler by Walter Bright, was originally released under a custom license, qualifying as source available but not conforming to the open source definition. In 2014 the compiler front-end was re-licensed as open source under the Boost Software License. This re-licensed code excluded the back-end, which had been partially developed at Symantec. On April 7, 2017, the entire compiler was made available under the Boost license after Symantec gave permission to re-license the back-end, too. On June 21, 2017, the D Language was accepted for inclusion in GCC.

    As of GCC 9, the D language frontend was merged into GCC.


    Most current D implementations compile directly into machine code for efficient execution.

    Using above compilers and toolchains, it is possible to compile D programs to target many different architectures, including x86, amd64, AArch64, PowerPC, MIPS64, DEC Alpha, Motorola m68k, Sparc, s390, WebAssembly. The primary supported operating system are Windows and Linux, but various compiler supports also Mac OS X, FreeBSD, NetBSD, AIX, Solaris/OpenSolaris and Android, either as a host or target, or both. WebAssembly target supported via LDC and LLVM can operate in any WebAssembly environment, like modern web browser Google Chrome, Mozilla Firefox, Microsoft Edge, Apple Safari, or dedicated Wasm virtual machines.

    Development tools

    Editors and integrated development environments IDEs supporting D include Eclipse, Microsoft Visual Studio, SlickEdit, Emacs, vim, SciTE, Smultron, TextMate, MonoDevelop, Zeus, and Geany among others.

    Open source D IDEs for Windows exist, some written in D, such as Poseidon, D-IDE, and Entice Designer.

    D applications can be debugged using any C/C++ debugger, like GDB or WinDbg, although support for various D-specific language features is extremely limited. On Windows, D programs can be debugged using Ddbg, or Microsoft debugging tools WinDBG and Visual Studio, after having converted the debug information using cv2pdb. The ZeroBUGS debugger for Linux has experimental support for the D language. Ddbg can be used with various IDEs or from the command line; ZeroBUGS has its own graphical user interface GUI.


    This example program prints its command line arguments. The main function is the entry point of a D program, and args is an array of strings representing the command line arguments. A string in D is an array of characters, represented by char[] in D1, or immutablechar[] in D2.

    1 import std.stdio: writefln;
    3 void mainstring[] args
    4 {
    5 foreach i, arg; args
    6         writefln"args[%d] = '%s'", i, arg;
    7 }

    The foreach statement can iterate over any collection. In this case, it is producing a sequence of indexes i and values arg from the array args. The index i and the value arg have their types inferred from the type of the array args.

    The following shows several D capabilities and D design trade-offs in a short program. It iterates over the lines of a text file named words.txt, which contains a different word on each line, and prints all the words that are anagrams of other words.

     1 import std.stdio, std.algorithm, std.range, std.string;
     3 void main {
     4     dstring[] [dstring] signs2words;
     6     foreach dchar[] w; linesFile"words.txt" {
     7 w = w.chomp.toLower;
     8         immutable key = w.dup.sort.release.idup;
     9 signs2words[key] ~= w.idup;
    10 }
    12     foreach words; signs2words {
    13         if words.length > 1 {
    14 writeflnwords.join" ";
    15         }
    16 }
    17 }


    Notable organisations that use the D programming language for projects include Facebook, eBay, and Netflix.

    D has been successfully used for AAA games, a JavaScript virtual machine, an operating system kernel, GPU programming, web development, numerical analysis, GUI applications, and a passenger information system.