Code That Says Exactly What It Means

[Kagamin]

On Thursday, 30 October 2025 at 17:53:15 UTC, Steven 
Schveighoffer wrote:
> If you look at it another way, you can't document usage with a 
> unittest that is not inside the module. There simply isn't a 
> way to tie an external unittest to the function, it has to go 
> right after it.
>
> This is a unittest problem, but in fact, it's very nice to have 
> the documented unittest required to be right after it (for 
> maintenance purposes). The better solution is to prevent 
> documented unittests (or at least provide the *ability* to 
> prevent) from accessing private data.

I'd say it's not wrong, private members should be documented. The 
problem looks more like ddoc doesn't differentiate between public 
and private documentation.