4 ms·
>> There are some bugs that have been resolved in the new llvm … Cool. >> Nightly rust let's you turn them on now I thinj … When they reach Stable … >> The
by igouy 9y ago
>> There are some bugs that have been resolved in the new llvm …
Cool.
>> Nightly rust let's you turn them on now I thinj …
When they reach Stable …
>> The output isn't checked to enough precision to …
Checked enough to have disallowed a new C++ program in the past few weeks ;-)
- galangalalgol 9y agoI had last run this comparison with rust 1.15. I reran it with 1.22 and they have added a few of the fixes. Unfortunately, none of them mattered for the n-body solution I was using. What is more, it was more than 10% slower than 1.15. Not impressed. I keep saying I want to try out rust as a c++ replacement where I work as soon as it settles down. I think that may he a while. The problem is that the rapid changes in c++ are causing us problems too as far as tool accreditation for safety and security. So a language that changes even faster is a non starter. But the comparable performance and superior safety guarantees is quite attractive in our case.
- steveklabnik 9y agoA lot of this kind of thing is due to upgrading LLVM, which I'd imagine should cause similar variance with clang, but maybe not!