DIPs VS Diamond

The reference compiler, DMD, is open source: https://github.com/dlang/dmd

But they don't accept just any Pull Request or features the community submits, understandably. There's a process called DIP for language improvements: https://github.com/dlang/DIPs/blob/master/DIPs/README.md

However, by some accounts, it's really hard to get anything through.

Given D already has so many feature, I find that to be a good thing , to be honest, by not everyone agrees, of course.

Borrow checking does not require lifetime annotations. D is a precedent there. Look at DIP25 and DIP1000.

There's no "nogc" containers in phobos, or allocators, or an idiomatic way to do safe manual memory management. It expects you to do it the C way. It's also impossible to implement some things because of how D does moving. There's a DIP in the works to change how moving works, but it's overly complicated and bound to introduce even more bugs. https://github.com/dlang/DIPs/blob/master/DIPs/DIP1040.md

D Is drafting up move semantics to interface better with C++. Although they're going a bit the Rust way in the current proposal. D has tried a couple of other strategies, but unique pointers and C++ interoperability kind of forced the hand of Walter Bright.

String interpolation is coming: https://github.com/dlang/DIPs/blob/master/DIPs/DIP1036.md