Advanced code coverage analysis

[thinwybk]

On Tuesday, 5 December 2017 at 12:39:53 UTC, Johan Engelen wrote:
> LDC's PGO output can be used for that. See [1]. Except that LDC 
> does not yet output full source mappings for the counters 
> (`-fcoverage-mapping`).
> Because the DMD frontend rewrites code besides semantic 
> analysis, it is problematic to create correct source mappings, 
> and I have thusfar refrained from implementing that.
> (For folks interested in contributing to LDC: it'd be a nice 
> project to work on, with nice incremental steps. It's quite 
> possible that there is already enough info in the IR for 
> IR-based (instead of current PGO instrumentation) 
> instrumentation/mapping to work well)

Advanced code coverage would have been a nice to have. Especially 
in the technical and/or embedded domain where DMD is in most 
cases no option anyway (LDC or GDC are the two choices here).

Unfortunately other projects have higher priority for me right 
now.