Inherent code performance advantages of D over C?

[Manu]

On 8 December 2013 03:33, Walter Bright <newshound2 at digitalmars.com> wrote:

> On 12/7/2013 1:45 AM, Joseph Rushton Wakeling wrote:
>
>> TL;DR the point is that writing in D gave me the opportunity to spend
>> mental and
>> programming time exploring these different choices and focusing on
>> algorithms
>> and data structures, rather than all the effort and extra LOC required to
>> get a
>> _particular_ idea running in C.  That's where the real edge arises.
>>
>
> I've noticed this too, but I've found it hard to explain to C programmers.
>
> To say it a different way, D makes it easy to refactor code to rapidly try
> out different algorithms. In C, one tends to stick with the original design
> because it is so much harder to refactor.
>

True as compared to C, but I wouldn't say this is true in general.
C# and Java make it easy to refactor code rapidly. D doesn't have any such
tools yet.
It's my #1 wishlist item for VisualD and Mono-D, and I await such tooling
with great anticipation.
Maybe when the D front-end is a library, and tooling has such powerful (and
reliable) semantic analysis as the compiler does it may be possible?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20131208/d1abaf3a/attachment.html>