diff options
| author | bors <bors@rust-lang.org> | 2014-10-17 05:42:19 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2014-10-17 05:42:19 +0000 |
| commit | 0f8df80804b2c7e89acc3c8e046a1ac7a90124f6 (patch) | |
| tree | 896a86f527b517ae7341ac0a14a6152394e261c9 /src/rustllvm/RustWrapper.cpp | |
| parent | 3dec727297e6ebd6614219a93f376d8181ab11b1 (diff) | |
| parent | 1a6f1ebad541e179f7418ce0102540cb15fb455e (diff) | |
| download | rust-0f8df80804b2c7e89acc3c8e046a1ac7a90124f6.tar.gz rust-0f8df80804b2c7e89acc3c8e046a1ac7a90124f6.zip | |
auto merge of #18056 : TeXitoi/rust/shootout-reverse-complement-improvement, r=alexcrichton
This is some improvement as asked and discused here: http://www.reddit.com/r/rust/comments/2j2ij3/benchmark_improvement_reverse_compliment/ Before: ``` real 0m0.396s user 0m0.280s sys 0m0.112s ``` after: ``` real 0m0.293s user 0m0.216s sys 0m0.076s ``` best C version: ``` real 0m0.135s user 0m0.132s sys 0m0.060s ``` Another possibility will be to add a `DoubleEndedIterator::next_two_side()` with a deffault implementation, and specialising it for slices, and use it here (`MutableSlice::reverse()` can then become safe). This benchmark will then be safe. What do you think?
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
