On Tuesday, 1 August 2017 at 20:37:16 UTC, Anton Fediushin wrote:
Thanks! Yes, module "covered.loader" can be used, but it isn't
complete yet. I'll start working on v1.0.0 tomorrow, changing
current design (get as much information as possible and store
it) to a new one (get only required inform
On Tuesday, 1 August 2017 at 08:19:47 UTC, Szabo Bogdan wrote:
Nice work!
I would like to contribute to such a tool :) I was working at
something similar with trial( http://trial.szabobogdan.com/ ),
and I would like to include your library if it's possible.
Thanks! Yes, module "covered.loade
On Monday, 31 July 2017 at 15:45:18 UTC, Anton Fediushin wrote:
On Monday, 31 July 2017 at 15:27:42 UTC, jmh530 wrote:
On Monday, 31 July 2017 at 13:06:44 UTC, Anton Fediushin wrote:
Hello! I am glad to announce a new command-line tool which
should make development
a little easier.
You cou
On Monday, 31 July 2017 at 15:27:42 UTC, jmh530 wrote:
On Monday, 31 July 2017 at 13:06:44 UTC, Anton Fediushin wrote:
Hello! I am glad to announce a new command-line tool which
should make development
a little easier.
You could add a mixin template that injects the
"version(D_Coverage)" c
On Monday, 31 July 2017 at 13:06:44 UTC, Anton Fediushin wrote:
Hello! I am glad to announce a new command-line tool which
should make development
a little easier.
You could add a mixin template that injects the
"version(D_Coverage)" code.
Hello! I am glad to announce a new command-line tool which should
make development
a little easier.
Program, compiled with `-cov` switch, generates *.lst files. They
contain program source, number of executions of each line and
total code coverage of the file.
Those files are quite useful for