Code That Says Exactly What It Means

Fustiki Scuria fustikiscuria at gmail.com
Sun Nov 2 18:36:51 UTC 2025


I'd like to say that I'd much rather see this as protected 
becoming non-mutually-exclusive with private, package, and 
public. It's already pretty much orthogonal to them and would 
have a very similar effect to scopeprivate without introducing a 
new keyword. This would make a private protected member only 
accessible to a subclass within the same module which would have 
to be a very deliberate choice (but not an invalid one, there can 
be uses for this, especially in recursive typed structure like 
ASTs). None of the semantics of the visibility modifiers 
particularly change and the use-case of scopeprivate is dealt 
with, for the most part.


More information about the Digitalmars-d mailing list