On Monday, 22 January 2024 at 23:28:40 UTC, Jonathan M Davis
wrote:
...
but it's not a feature that has actually been causing us
problems, and it really doesn't make sense at this point to
change how it works.
- Jonathan M Davis
I don't agree.
The first time I used the D language, I discovered a 'problem'.
That is, my unittest inadvertently accessed a private member of a
class, instead of using the public interface of the class.
Now the problem of course was me, the programmer (at least one
could argue that).
But to me, the problem was the language, for not having a feature
that could have avoided this problem in the first place.
Now, if I want to use D to program, I have to ensure I don't make
the same mistake again, by putting my unittest into there own
source files (since the compiler cannot warn me, since the
language has no feature to make my intent explicit to it).
That problem has not gone away, and nor can it, without splitting
up everything it own source file.
Whether it makes sense to change it now, is a separate argument
(and not really one I want to get into, since the arguments
against it are always just fluff, and not worthy of my attention).
But the argument that it cannot cause a problem, is already shown
to be wrong.
