Code coverage in Phobos

[Seb via Digitalmars-d]

On Tuesday, 29 March 2016 at 20:50:57 UTC, Seb wrote:
> Okay I see that for the long run we need a better way to handle 
> the testing infrastructure :/

Actually the idea of achieving "100% coverage" is that we test 
every line at least once and don't let this testing by done by 
users.
So to refresh the discussion - there were two general ideas

1) Find "bad", "dangerous" modules, e.g.

/xml.d 64%
/zlib.d 60%
/experimental/allocator/typed.d 54%
/experimental/allocator/building_blocks/segregator.d 50%
/experimental/allocator/building_blocks/bucketizer.d 48%
/encoding.d 66%
/container/binaryheap.d 59%
/digest/digest.d 72%

2) Increase coverage for generic, platform-independent modules 
like std.algorithm to 100%

I know it's a lot of work, but shouldn't that make our jobs us 
maintainers easier (=catch the bugs before you have to fix 
them?). Therefore I am bumping this ;-)