scratchpad
A Rust library providing a stack-like memory allocator with double-ended allocation support.
Note: scratchpad
is currently in maintenance mode. I've been considering
doing a major cleanup for some time to get rid of extraneous functionality and
reduce the surface area of unsafe
code, but there is currently no timeline
for this. I'll still apply fixes as needed, but development has otherwise
stalled.
Scratchpad
provides a method for quick and safe dynamic allocations of
arbitrary types without relying on the global heap (e.g. using Box
or
Vec
). Allocations are made from a fixed-size region of memory in a
stack-like fashion using two separate stacks (one for each end of the
allocation buffer) to allow different types of allocations with independent
lifecycles to be made from each end.
Such allocators are commonly used in game development, but are also useful in general for short-lived allocations or groups of allocations that share a common lifetime. While not quite as flexible as heap allocations, allocations from a stack allocator are usually much faster and are isolated from the rest of the heap, reducing memory fragmentation.
Features include:
- User-defined backing storage of data (static arrays, boxed slices, or mutable slice references).
- Allocation of any data type from any scratchpad instance.
- Ability to combine allocations that are adjacent in memory or add to the most recently created allocation.
- Double-ended allocation support (allocations from the "front" are separate from the "back", but share the same memory pool).
- Use of lifetimes to prevent dangling references to allocated data.
- Low runtime overhead.
- Support for
no_std
usage.
Usage
Add this to your Cargo.toml
:
[]
= "1.3"
For Rust 2015 code, also add this to your crate root:
extern crate scratchpad;
Rust Version Support
The minimum supported Rust version is 1.25 due to use of NonNull<T>
and the
repr(align)
attribute.
no_std
Support
scratchpad
doesn't require the Rust standard library, although it makes use
of it by default (via the std
crate feature) to provide support for use of
Box
and Vec
in various places. For no_std
support, the std
feature
must be disabled in your Cargo.toml
:
[]
= { = "1.3", = false }
Box
and Vec
support is still available for no_std
builds by enabling the
alloc
feature, which uses the alloc
crate directly:
[]
= { = "1.3", = false, = ["alloc"] }
The alloc
feature requires Rust 1.36.0 or later. Older versions of the
nightly toolchain can still use Box
and Vec
in no_std
code via the
unstable
feature.
Unstable Features
The unstable
crate feature provides some additional functionality when using
a nightly toolchain:
- Declaration of the function
Scratchpad::new()
asconst
. - Support for various features that were still unstable with legacy Rust
releases:
Box
andVec
support forno_std
code (enabled without theunstable
feature when using Rust 1.36.0 or later with thealloc
feature enabled).ByteData
trait implementations foru128
andi128
(enabled without theunstable
feature when using Rust 1.26.0 or later).ByteData
trait implementation for allstd::mem::MaybeUninit
types wrapping otherByteData
types (enabled without theunstable
feature when using Rust 1.36.0 or later).
Simply add the unstable
feature to your Cargo.toml
dependency:
[]
= { = "1.3", = ["unstable"] }
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.