Removing all C++ compatibility is a death sentence for D. This
may not be apparent to some people that already program in D, but
it is downright critical to potential D users. Zero C++
compatibility means that D can no longer interface with C++
libraries such as Qt, putting a severe limitatio
On Wednesday, 14 June 2017 at 12:08:16 UTC, Mike wrote:
> THINGS TO DROP
--
* C++ interoperabiliy
Walter's right: memory safety is going to kill C and C++ will
go with it. Don't waste time on this; it's not going to matter
in 10 or 20 years.
Thank you for making a list to give peo
On Sunday, 11 June 2017 at 00:27:06 UTC, ketmar wrote:
..and it actually should be D1.5, not D3. ;-) 'cause D3 implies
even more features, and i feel that the way to get The Perfect
D (sorry! ;-) is trying to cut all the features that aren't
strictly necessary (including fat-free stdlib too: i
D is a language with much promise, but it still has many problems
that prevent it from being the great replacement for C++ that it
was always meant to be.
There have been many changes suggested over time to improve the
language, but they were rejected as they would inevitably cause
breaking c
