On Wednesday, 6 December 2017 at 06:05:32 UTC, Basile B. wrote:
Indeed, but there's still some room for a tool. I'd add this to
my IDE since for now coverage is not indicated in the code
editor but in the messages (a message for each line that's not
covered).
Anyway it's a two days project
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
On Wednesday, 6 December 2017 at 03:15:38 UTC, Walter Bright
wrote:
On 12/5/2017 2:55 AM, Basile B. wrote:
On Monday, 4 December 2017 at 20:33:56 UTC, thinwybk wrote:
Hi everyone,
as far as I know there is a statement coverage analyzer built
into DMD https://dlang.org/code_coverage.html . Are
On 12/5/2017 2:55 AM, Basile B. wrote:
On Monday, 4 December 2017 at 20:33:56 UTC, thinwybk wrote:
Hi everyone,
as far as I know there is a statement coverage analyzer built into DMD
https://dlang.org/code_coverage.html . Are there code coverage analyzers for D
which support branch coverage a
On Monday, 4 December 2017 at 20:33:56 UTC, thinwybk wrote:
Hi everyone,
as far as I know there is a statement coverage analyzer built
into DMD https://dlang.org/code_coverage.html . Are there code
coverage analyzers for D which support branch coverage and
other more advanced coverage metrics
On Monday, 4 December 2017 at 20:33:56 UTC, thinwybk wrote:
Hi everyone,
as far as I know there is a statement coverage analyzer built
into DMD https://dlang.org/code_coverage.html . Are there code
coverage analyzers for D which support branch coverage and
other more advanced coverage metrics
