diff options
| author | bors <bors@rust-lang.org> | 2013-03-30 19:51:40 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-03-30 19:51:40 -0700 |
| commit | bd7ba1fa62e5569a1a7c6335ff7b2a334cff2ad0 (patch) | |
| tree | 0fbeeb24ee1d644875fb559127abee879aa44502 /src/rt/rust_run_program.cpp | |
| parent | 8e30d3fc0bad3bac9f5f1fc2b925aa831aca8ff8 (diff) | |
| parent | 258a36738e6dcba1b01609e026862aa9750ccdbd (diff) | |
| download | rust-bd7ba1fa62e5569a1a7c6335ff7b2a334cff2ad0.tar.gz rust-bd7ba1fa62e5569a1a7c6335ff7b2a334cff2ad0.zip | |
auto merge of #5634 : thestinger/rust/dlist, r=brson,thestinger
Closes #3549 The issue report has some reasoning, but I'd like to add that I don't think managed pointers belong in core. It's *possible* to write a safe doubly-linked list on top of `unsafe`, but it would be much more limited and I don't think there's much of a use case - it would lose a lot of flexibility. You're probably better off using a vector, hash table, tree, heap or ring buffer in almost every case.
Diffstat (limited to 'src/rt/rust_run_program.cpp')
0 files changed, 0 insertions, 0 deletions