Code That Says Exactly What It Means

[Sergey]

On Tuesday, 28 October 2025 at 06:47:14 UTC, Peter C wrote:
> Conceptually, it works well as it fits my mental model, and

Good for you!

> programmatically it works well also. The module boundary of the 
> member is not affected, unless the programmer opts-in to using 
> scopeprivate. There are no breaking changes. Everyones code 
> will still compile. So what's the problem then?

There is no problems as I can see.
You wanted this feature - you've implemented it and now you can 
use it.
It's not going to happen in upstream D.
You can speak with Adam and try to include it into OpenD.

> Slightly off topic now:
> Even after more that two decades of devlopment, the D 
> Programming Language didn't even get a single mention. It's not 
> that it was mentioned and then discarded as not being a 
> suitable succesor for this or that reason, it just wasn't 
> mentioned. Not even a mention from the audience at question 
> time. This was just last year! I was pretty suprised by this 
> actually.

The real reason : 
https://x.com/cyrus_msk/status/1855399721998876761