On Saturday, 2 June 2018 at 12:49:45 UTC, Microbe wrote:
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?
Microbe, if you were a keyword for a protection attribute in a
programming language, i would choose "smuck".
