Slower than Python

[Jacob Carlborg]

On 2013-03-04 09:18, Jonathan M Davis wrote:

> Given how D works, there is something _very_ wrong if we have to drop to C, if
> nothing else, because it's trivial to write code in D which is equivalent to
> what it would be in C. If our implementation of something is worse than a C
> implementation, that merely means that it needs to be refactored and
> optimized. It's possible that some of our abstractions will hamper efficiency in
> some cases (e.g. depending on how ranges are used - particularly with strings
> - you risk a performance hit in comparison to pure C), but that should
> generally be fixable via specializations and whatnot.
>
> If we have an efficiency problem, it's merely an implementation issue which
> needs to be sorted out. There should be nothing inherent to D which makes it
> so that you can't write code as fast as C or C++.

That's what I'm saying.

-- 
/Jacob Carlborg