Is public by default an unsafe default?

[Alexandru Ermicioi]

On Wednesday, 8 May 2024 at 00:22:59 UTC, Walter Bright wrote:
> Being public or private has nothing to do with memory safety.

I don't think he even talks about memory safety in first place, 
but rather general safety. It seems a lot of people hearing 
safety think memory safety in this discussion.

> Private is of interest only when complexity exceeds a certain 
> threshold.
That is, if developers improving the module are pedantic 
developers.

Developers just doing their work at an job may not hassle to put 
private at all, spilling most of internals into exterior, which 
could easily be used without awareness by other team members.