Driving Continuous Improvement in D

[Microbe]

On Saturday, 2 June 2018 at 07:23:42 UTC, Mike Parker wrote:
> In this post for the D Blog, Jack Stouffer details how dscanner 
> is used in the Phobos development process to help improve code 
> quality and fight entropy.
>
> The blog:
> https://dlang.org/blog/2018/06/02/driving-continuous-improvement-in-d/
>
> reddit:
> https://www.reddit.com/r/programming/comments/8nyzmk/driving_continuous_improvement_in_d/

As you know, surrounding code within a module can infilitrate the 
membrane structure of those types that use 'private' to protect 
their boundary (for example, the 'private' member in that struct, 
in that blog).

Since the compiler is completely useless in such situations (as 
it conspires with the surrounding code 'to ensure that it can 
infiltrate your types'), what does dscanner bring to the table, 
if anything, to help the programmer to ensure such types don't 
die a quick death due to the cytotoxic effect the module has on 
such types?

Or is this not considered a 'quality' issue in D?