D for scientific computing

[Andrei Alexandrescu]

On 1/24/13 5:21 AM, deadalnix wrote:
> On Thursday, 24 January 2013 at 02:19:06 UTC, Era Scarecrow wrote:
>> On Thursday, 24 January 2013 at 00:35:13 UTC, Joshua Niehus wrote:
>>> On Thursday, 24 January 2013 at 00:29:15 UTC, Joshua Niehus wrote:
>>>> You don't need to compete, you can take established "good and fast"
>>>> FORTRAN/C code and use it within your own D program.
>>>
>>> I forgot to add:
>>> If you doing new stuff then D can be as fast as anything eles,
>>> provided the algorithm is sound, optimizers turned on, sprinkle in a
>>> lil assembly, etc...
>>
>> And use nothrow when it's applicable; Found with a sudoku solver how
>> much nothrow was making an impact on the algorithm speed.
>
> Do you know why ? It shouldn't.

More code motion. It's a classic in C++ code as well (where it's mode 
difficult to detect).

Andrei