package & protected?

[Max Samukha]

On Monday, 21 October 2024 at 07:49:18 UTC, Manu wrote:

>
> This is a problem. We need a way to express both... what's the 
> story here?

I guess the answer would be: it's your package, so you control it 
and don't need to protect it from yourself. At least, that was 
part of the argument against class-private (as I understood it): 
the module is the API boundary, why would you protect anything 
inside? Ironically, packages are not sealed, so 'package' doesn't 
really protect anything at all.