Petar Kirov

> supporting older versions of libclang as long as it doesn't cause extra work You can get a very rough approximation of the amount of work necessary to support different...

Nice work, Adam! Do you have some sort of CI diff tool like DAutoTest that can show the diff between two versions of the doc engine or two versions of...

I think the best way to get full featured vim support (including vim plugins) is to use nvim as a library. There are plenty of electron js projects that do...

If you guys use dfmt as a library, you could probably directly use this: https://github.com/dlang-community/dfmt/blob/master/src/dfmt/editorconfig.d

I tried a couple of things with the current layout, but I couldn't figure out how to make it `@safe`. So far, I'm thinking that only a layout like this...

> It should track the lifetime of the returned range as being shorter than the vector that returned it (because of return scope) then disallow assigning it to a global....

One possible way to do this may be to pre-allocate an array of records for each unittest. Inside the assert\* functions the code will then fill the corresponding record for...

To clarify about my idea to use fibers - instead of throwing DUnitAssertError, you can fiber.yield() directly to the code that is supposed to catch the exception

What's the motivation for doing so? `fakePureErrno` was added to druntime specifically for `std.experimental.allocator` and to avoid code duplication like this.

List of things that should be moved to druntime: * `std.internal.memory` -> `core.memory` * `std.conv.emplace` -> `core.lifetime` * `std.experimental.allocator` -> `core.memory.allocator` Why? So we can reimplement the built-in AAs and...