Final by default?

[Daniele Vian]

On Thursday, 13 March 2014 at 10:19:09 UTC, Andrej Mitrovic wrote:
> Another important point to make: If client A says a specific 
> changeset
> was bad, what gives client A priority over client B who says 
> the same
> changeset is good? These clients need to  communicate directly 
> with
> the community and the developers via the forums and by filing
> bugs/enhancement reports.
>
> I believe clients (why are we calling them "clients" anyway?) 
> should
> have to provide reasonable arguments for preferring one feature 
> over
> another, beyond the simple "we're using D therefore we're 
> important"
> argument.

Just to be clear, I never had a "preferred" implementation, nor I 
would ever "lobby" for one as it's not in the best interest of 
anybody.
Consider me a fan of breaking the code if it improves features, 
security and what not.
The only thing I'm asking for is for it to be transparent: a 
point in the changelog and keeping the old one as deprecated for 
a reasonable amount of time, that's all.

A bug was not filed as it didn't look like a bug but a design 
choice (undocumented).
If reporting it directly to Walter Bright was the wrong thing to 
do, my apologies, but we surely didn't have any hidden "agenda" 
here.

Thanks
Daniele