Brian Schott

You're missing the point. For something like Textadept, SciTE, or Nodepad++ a D plugin could ask Scintilla for the current line and column numbers when the cursor is at the...

To really work properly this would require D-Scanner to be a LOT more intelligent than it currently is.

There are a few ways to go about this. 1. Check to see if the AST of the left side is the same as the right. This is really easy...

I started thinking about implementing this and realized that we'd need a way to provide import paths so that the DSymbol code can figure things out using imported modules. Then...

It's probably a better idea to implement this in the compiler than in D-Scanner.

This is going to be harder than it seems to implement. Besides that, some editors require that the completion lists be sorted alphabetically (e.g. anything based on Scintilla)

http://www.scintilla.org/ScintillaDoc.html#SCI_AUTOCSHOW Implementing the type deduction would require some nontrivial error recovery in the parser.

You mean the ratio of SLOC inside `unittest` blocks vs outside? Or did you want some sort of code coverage calculation?

Something like this? ``` $ dcd-client --list-environments ☐ nightly-dmd ☑ latest-dmd ☐ latest-ldc ☑ gtkd ☑ libdparse ``` ``` $ dcd-client --disable latest-dmd --enable nightly-dmd ```

> (not sure if currently possible, but if not: there should also be a way to reload all files from a folder in case where the dependency/environment is a git...