Go to file
Stjepan Glavina 0eb4ea496c Implement get_(mut_)unchecked 2017-04-03 14:06:33 +02:00
examples Don't specify capacity in splay tree 2016-12-20 18:49:45 +01:00
src Implement get_(mut_)unchecked 2017-04-03 14:06:33 +02:00
.gitignore Rough initial design 2016-10-23 14:58:49 +02:00
.travis.yml Add Travis config 2016-10-25 17:54:37 +02:00
Cargo.toml Add repository to Cargo.toml 2016-11-15 00:34:25 +01:00
LICENSE-APACHE Change to dual Apache-2.0/MIT 2016-10-25 18:54:42 +02:00
LICENSE-MIT Change to dual Apache-2.0/MIT 2016-10-25 18:54:42 +02:00
README.md Update documentation 2016-11-14 23:43:36 +01:00

README.md

vec-arena

Build Status License Cargo Documentation

What is this?

A simple object arena.

You want to build a doubly linked list? Or maybe a bidirectional tree? Perhaps an even more complicated object graph?

Managing ownership and lifetimes might be tough then. Your options boil down to:

  1. Use unsafe code to escape Rust's ownership rules.
  2. Wrap every object in Rc<RefCell<T>>.
  3. Use Vec<T> to store objects, then access them using indices.

If the last option seems most appealing to you, perhaps Arena<T> is for you. It will provide a more convenient API than a plain Vec<T>.

Examples

Some data structures built using Arena<T>: