diff options
| author | bors <bors@rust-lang.org> | 2013-04-20 01:00:49 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-04-20 01:00:49 -0700 |
| commit | 4ff701b7db609cabe59832d47779832a16627b5f (patch) | |
| tree | 49317e2439d493b798412dad2c92b60e366f229f /src/libcore/vec.rs | |
| parent | 028dc589d1cfb7e44b36b978ea1dcc304d70cee0 (diff) | |
| parent | cd982ad3f74673c55af6034a4f757e60be9b381c (diff) | |
| download | rust-4ff701b7db609cabe59832d47779832a16627b5f.tar.gz rust-4ff701b7db609cabe59832d47779832a16627b5f.zip | |
auto merge of #5965 : alexcrichton/rust/issue-4364, r=pcwalton
This closes #4364. I came into rust after modes had begun to be phased out, so I'm not exactly sure what they all did. My strategy was basically to turn on the compilation warnings and then when everything compiles and passes all the tests it's all good. In most cases, I just dropped the mode, but in others I converted things to use `&` pointers when otherwise a move would happen. This depends on #5963. When running the tests, everything passed except for a few compile-fail tests. These tests leaked memory, causing the task to abort differently. By suppressing the ICE from #5963, no leaks happen and the tests all pass. I would have looked into where the leaks were coming from, but I wasn't sure where or how to debug them (I found `RUSTRT_TRACK_ALLOCATIONS`, but it wasn't all that useful).
Diffstat (limited to 'src/libcore/vec.rs')
0 files changed, 0 insertions, 0 deletions