From 2bc4d3ec23cc88155173729e60df54c8aa4949a6 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Fri, 24 Oct 2014 17:34:57 -0400 Subject: get rid of libc_heap::{malloc_raw, realloc_raw} The C standard library functions should be used directly. The quirky NULL / zero-size allocation workaround is no longer necessary and was adding an extra branch to the allocator code path in a build without jemalloc. This is a small step towards liballoc being compatible with handling OOM errors instead of aborting (#18292). [breaking-change] --- src/liballoc/lib.rs | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) (limited to 'src/liballoc/lib.rs') diff --git a/src/liballoc/lib.rs b/src/liballoc/lib.rs index 2df9a585fec..c721649ca9d 100644 --- a/src/liballoc/lib.rs +++ b/src/liballoc/lib.rs @@ -54,11 +54,8 @@ //! //! ## Heap interfaces //! -//! The [`heap`](heap/index.html) and [`libc_heap`](libc_heap/index.html) -//! modules are the unsafe interfaces to the underlying allocation systems. The -//! `heap` module is considered the default heap, and is not necessarily backed -//! by libc malloc/free. The `libc_heap` module is defined to be wired up to -//! the system malloc/free. +//! The [`heap`](heap/index.html) module defines the low-level interface to the +//! default global allocator. It is not compatible with the libc allocator API. #![crate_name = "alloc"] #![experimental] @@ -90,7 +87,6 @@ pub use boxed as owned; // Heaps provided for low-level allocation strategies pub mod heap; -pub mod libc_heap; // Primitive types using the heaps above -- cgit 1.4.1-3-g733a5