4 ms·
In some problems Rust is the fastest: https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/nbody.html https://benchmarksgame-team.pages.debi
by bufferoverflow 6y ago
In some problems Rust is the fastest:
https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/nbody.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/spectralnorm.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/revcomp.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/binarytrees.html https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
- jonny383 6y agoEvery single one of those rust implementations is using unsafe {}, thus defeating the purpose of using rust in the first place. Run the same benchmark without unsafe {}.
- turndown 6y ago>defeating the purpose of using rust in the first place I don't think this is true; the whole point of Rust is that unsafe operations are explicit, not that you never do so. Also, I looked at the first one, and it's only using unsafe on what are basically op code calls; I don't think it is realistic to complain about that.
- igouy 6y agoNot true. Of those 4 tasks, the rust programs for task 3 and task 4 do not use the keyword "unsafe". For task 2, the spectral-norm Rust #6 program does use "unsafe" but #5 does not and it's almost as fast.