rusty_alloc-api 2.6.0

Safe Rust surface for the rusty_alloc pure-Rust mimalloc remake: GlobalAlloc, first-class Heap, and the Allocator trait. No unsafe required of callers. MIT.
Documentation
[package]
name = "rusty_alloc-api"
description = "Safe Rust surface for the rusty_alloc pure-Rust mimalloc remake: GlobalAlloc, first-class Heap, and the Allocator trait. No unsafe required of callers. MIT."
documentation = "https://docs.rs/rusty_alloc-api"
version.workspace = true
edition.workspace = true
license.workspace = true
repository.workspace = true
homepage.workspace = true
rust-version.workspace = true
authors.workspace = true
keywords.workspace = true
categories.workspace = true
readme = "README.md"

[dependencies]
# A published crate needs a VERSION alongside the path: the path is what the
# workspace builds against, the version is what crates.io resolves.
rusty_alloc = { path = "../rusty_alloc", version = "2.6.0", default-features = false }

[features]
# Mirrors the core's (P3, docs/plans/small-metal.md). Default-on, so every
# existing consumer is unchanged; a firmware takes `default-features = false`
# and gets the single-heap no_std profile. This crate's own source has been
# `no_std` since M2 — only the dependency's default features stood in the way.
default = ["std"]
std = ["rusty_alloc/std"]
debug_checks = ["rusty_alloc/debug_checks"]
profile = ["rusty_alloc/profile"]
secure = ["rusty_alloc/secure"]
# `core::alloc::Allocator` for `RustyAlloc` and `Heap`. The trait is stable
# from Rust 1.100, which is above this crate's `rust-version`, so it is opt-in:
# without the feature the crate builds on its declared minimum, and with it an
# older compiler stops at `use of unstable library feature 'allocator_api'`.
# It becomes unconditional when the minimum reaches 1.100.
allocator-api = []

[package.metadata.docs.rs]
features = ["allocator-api"]

[lints]
workspace = true