Preparing for the New DIP Process

[Jordan Wilson]

On Friday, 26 January 2024 at 23:41:51 UTC, FairEnough wrote:
> On Thursday, 25 January 2024 at 00:19:54 UTC, Jordan Wilson 
> wrote:
>>
>> ...
>> That wasn't what was said. What was said was "causing US 
>> problems". I.e. on the whole, the lack of class-level privacy 
>> does not appear to be causing widespread problems, which 
>> implies that it's simply lower on the list of feature requests 
>> for most people.
>>
>
> Allowing mutable state to escape - the confines of the type in 
> which it has been declared - into the whole of the module, will 
> inevitably lead to a problem.
>
> My first use of the D language demonstrated that this statement 
> is factual.

When I first used a dynamically typed language, I was inevitably 
caught out by type errors. I understood this to be part of the 
many trade offs all languages make.

> The more 'widespread' D is used, will 'likely' also demonstrate 
> the same.

I suspect the proportion of users that really care about explicit 
class privacy and find the workaround of putting a class that 
needs such privacy into a separate file untenable, will remain 
the same.

Jordan