![\"\"](\"http:\/\/dlang.org\/blog\/wp-content\/uploads\/2016\/08\/d3.png\")
2018 was one of the biggest years in D we\u2019ve had for a while. It was the first complete year that DMD stuck to a steady release schedule. Over the course of the year, the language got new features and cruft cleanup. The compiler even got some new user-facing features. At the same time, the community-at-large continued to evolve the surrounding ecosystem.<\/p>\n
The first DMD release of the year was version 2.078 on January 1<\/a>. It set the tone for much of the year, including more support for a stripped-down runtime<\/a> for The next major release came out in March<\/a>, and I personally found it to be the most exciting release in a couple of years because it came with improved error messages<\/a> – notably, calling out the specific argument to a function that mismatched a type (though I will note there is still a lot of room for further improvement!). Moreover, this release introduced DMD\u2019s Meanwhile, more stripped-down runtime support and general language cleanup was included in the release. March also introduced experimental March was also the first time DMD on Windows could do a total build of a 64-bit program without Visual Studio installed because it bundled the LLVM linker<\/a>.<\/p>\n Keeping to the release schedule, May and July brought us new major versions, which focused on language cleanup, with a lot of deprecations. There was a #dbugfix campaign over the year<\/a>, and it brought a fix in May\u2019s release<\/a>: allowing the Version 2.082<\/a>, in September, finally brought me something I have wanted for a long time: User Defined Attributes<\/a> on At the end of the year, version 2.083<\/a> saw extern(C++) get a big improvement its users have been waiting for: namespaces without scopes<\/a>, which makes C++ interoperability and code organization a lot easier. Work on making the C++ standard library accessible from D has been progressing throughout the year.<\/p>\n Overall, the year brought a lot of awaited improvements. D is more usable in various runtime library situations (even Phobos has some Debugging got better, with the uncaught exception switch, but also allowing the Of course, the library continued to get better range support and its support for And as a fun fact, DMD is now 98% ported to D, with another major part converted over the year.<\/p>\n More companies invested in D in 2018. Hosted by QA Systems<\/a>, DConf 2018 was held<\/a> in Munich, Germany, the first time DConf has been to that city (and the third time in Germany, after taking place in Berlin in 2016<\/a> and 2017<\/a>). Symmetry Investments sponsored the successful Symmetry Autumn of Code<\/a>, funding three students to work on D-related projects.<\/p>\n run.dlang.io came out<\/a> at the end of 2017 and grew in popularity throughout 2018, becoming the new standard for running D code online, including from the dlang.org homepage<\/a>. It even supports a whitelist of third-party libraries.<\/p>\n The dlang-tour website<\/a> gained a few new translations from the community, including Vietnamese, Portugese, French, Turkish, German, and Ukrainian.<\/p>\n The D Language Foundation was busy in 2018 as well. They received over $5000 on Open Collective<\/a>, $3000 of which was earmarked to support development of the code-d VS Code plugin<\/a> and the language server<\/a> that drives it. With a successful campaign launched through Flipcause<\/a>, the DLF was able to hire a pull request manager for three months. Donations through all platforms<\/a> allowed them to fund some outreach efforts as well as student work via scholarships. To increase visibility, they submitted a history of D paper to the Fourth ACM SIGPLAN History of Programming Languages Conference<\/a>.<\/p>\n Over 2,500 pull results have now been merged by the dlang-bot on GitHub, and the Project Tester has now gained 50<\/sub> projects that it tests on every PR to give real-world data on compiler regressions and the impact of breakages.<\/p>\n DIP 1014, \u201cHooking D\u2019s struct move semantics\u201d<\/a>, was also accepted. It will open some doors that were closed by design in old D, but that many developers had found limiting. Before, the compiler could move your structs whenever it wanted. Now, it will be hookable to give more control to the programmer and avoid a nasty case of bugs.<\/p>\n I opened up my documentation generation website at dpldocs.info<\/a> to all DUB projects this year, and upstream linked to it, encouraging D library authors to better document their libraries and allowing users to better evaluate the libraries before downloading them.<\/p>\n On Twitter, @dlang_ng was started<\/a> and has gained about 200 followers. All announcement topics from the Announce forum<\/a> (aka the digitalmars.D.announce newsgroup<\/a>) are tweeted out here.<\/p>\n 2018 also saw community announcements of the autowrap and dpp projects. autowrap automatically wraps<\/a> existing D code to be used from other environments, while dpp runs a C pre-processor over D code<\/a> to make it possible to use C headers, unmodified, macros and all, directly in D. These two projects show the community\u2019s desire to integrate D more fully into existing codebases and projects.<\/p>\n Of course, not all is perfect in the D development community, including a few areas where this author would like to see improvement.<\/p>\n The most +1-ed PR on DMD, a string interpolation implementation<\/a> (and a very elegant approach in this writer\u2019s opinion), remains open and of uncertain status, despite a renewed effort to get it merged in December. Similarly, the State of D 2018 Survey<\/a> identified several areas for improvement<\/a>. Very few of these came to pass in 2018, though some progress was made. We deprecated some cruft, but auto-decoding, one of the top-five disliked Phobos features in the survey and one often derided in the forums, remains in place. We are still using Bugzilla, which got an average of 3.27 satisfaction rating out of a possible 5 stars in the survey. We achieved fewer regressions, but added even more to the attribute bloat. We have an official blog<\/a> and the annual DConf<\/a>, but the D Language Foundation\u2019s inner workings are still opaque.<\/p>\n It would be great if some of these weak points are addressed among the improvements and changes in 2019.<\/p>\n The code.dlang.org website<\/a> received some criticism in 2017, and it was addressed in 2018. The site got a new front page with usage statistics and project ranking based on GitHub info. The DUB program itself got faster and more stable, no longer going online on every run to check for updates, and achieving better online uptime.<\/p>\n The Mir library<\/a>, which has algorithms, collections, and more written to be 100% 2018 was a really good year for D. There is still much work to do, but worthwhile developments in all facets of the language and ecosystem gave me renewed excitement going into 2019. I expect that March 2019 release of D is going to be another big step toward improving the best programming language we have on Earth today!<\/p>\n Adam Ruppe is the author of D Cookbook<\/a> and maintainer of This Week in D<\/a>. Modules from his freely available arsd package<\/a> are used throughout the D community. He is also known for his legendary DConf 2014 presentation<\/a>.<\/em><\/p>\n There were a total of 166 contributors listed on the DMD changelog in 2018. Special thanks to them and to all the others in the D community who flesh out the ecosystem and make our favorite programming language!<\/p>\n 2018 was one of the biggest years in D we\u2019ve had for a while. It was the first complete year that DMD stuck to a steady release schedule. Over the course of the year, the language got new features and cruft cleanup. The compiler even got some new user-facing features. At the same time, the […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[15,6,9],"tags":[],"_links":{"self":[{"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/posts\/1924"}],"collection":[{"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/comments?post=1924"}],"version-history":[{"count":3,"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/posts\/1924\/revisions"}],"predecessor-version":[{"id":1927,"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/posts\/1924\/revisions\/1927"}],"wp:attachment":[{"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/media?parent=1924"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/categories?post=1924"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dlang.org\/blog\/wp-json\/wp\/v2\/tags?post=1924"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}-betterC<\/code> mode, and a deprecation change in arithmetic rules<\/a>.<\/p>\n-i<\/code> flag<\/a>, which automatically includes imported modules and has proven to be a major convenience to me over the year.<\/p>\n@nogc<\/code> exception throwing<\/a> (as proposed in DIP1008<\/a>). This release also changed the garbage collector<\/a> to be lazily initialized, part of the effort to make things cheaper and pay-as-you-go.<\/p>\npow<\/code> operator (^^<\/code>) and several std.math<\/code> functions to be used at compile time<\/a>. July\u2019s release<\/a> brought a change in contract syntax<\/a>, based on the proposal in DIP 1009<\/a>, allowing small expressions instead of requiring whole blocks.<\/p>\nenum<\/code> members and function parameters<\/a>, as well as the ability to disable DRuntime\u2019s exception trapping<\/a> via the --DRT-trapExceptions=0<\/code> runtime command-line switch, which allows for easier debugging of uncaught exceptions. Moreover, with this release the D Language Foundation began digitally signing the Windows binary releases<\/a>, which has helped smooth out the end-user experience when installing and running DMD. It should continue to help solve the false-positive problem we have seen with some virus scanners.<\/p>\n-betterC<\/code> support, like RefCounted<\/code> and Tuple<\/code>!). The language had over ten deprecations of old cruft like comma expressions, read-modify-write on shared, comma expressions, class allocators (did you even know D still had class allocators? To be honest, I thought they were formally deprecated years ago, but it was actually 2018 when the change officially happened!), and more.<\/p>\ndebug<\/code> statement to escape more attribute restrictions, better error messages out of the compiler, and a -verrors=context<\/code> switch to show the line right in the message. -betterC<\/code> debugging aids also improved, with the C assert function being a possibility. I\u2019ll also note that 2019 is already moving further\u2014new assert<\/code> printing code was merged just recently; we can choose how to control them and whether to use D or C facilities!<\/p>\n@nogc<\/code> and -betterC<\/code> has grown as well.<\/p>\nThe D Community<\/h2>\n
The DUB Package Manager<\/h2>\n
-betterC<\/code> compatible (which, of course, means it also works in all other D environments, too), is now the fifth-most popular package on the DUB registry, while the unit testing library unit-threaded<\/a> takes the third-place slot. First, second, and fourth are all related to vibe.d<\/a>, which is the project DUB was originally created to support.<\/p>\nConclusion<\/h2>\n
\n
\nAddendum<\/h2>\n
\n