smol-rs
/
vec-arena
mirror of https://github.com/smol-rs/vec-arena
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
49 Commits 1 Branch 3 Tags 117 KiB
Rust 100%
Go to file
Stjepan Glavina f533229a0a Bump to 0.5.0, delete unsafe, use 2018 edition 2020-07-07 09:35:12 +02:00
examples Bump to 0.5.0, delete unsafe, use 2018 edition 2020-07-07 09:35:12 +02:00
src Bump to 0.5.0, delete unsafe, use 2018 edition 2020-07-07 09:35:12 +02:00
tests Bump to 0.5.0, delete unsafe, use 2018 edition 2020-07-07 09:35:12 +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 Bump to 0.5.0, delete unsafe, use 2018 edition 2020-07-07 09:35:12 +02: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 Bump to 0.5.0, delete unsafe, use 2018 edition 2020-07-07 09:35:12 +02: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>: