2014-05-13 18:10:05 -05:00
|
|
|
// Copyright 2014 The Rust Project Developers. See the COPYRIGHT
|
|
|
|
// file at the top-level directory of this distribution and at
|
|
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
|
|
// option. This file may not be copied, modified, or distributed
|
|
|
|
// except according to those terms.
|
|
|
|
|
2014-08-04 05:48:39 -05:00
|
|
|
//! # The Rust core allocation library
|
2014-05-13 18:10:05 -05:00
|
|
|
//!
|
|
|
|
//! This is the lowest level library through which allocation in Rust can be
|
2014-10-28 16:06:06 -05:00
|
|
|
//! performed.
|
2014-05-13 18:10:05 -05:00
|
|
|
//!
|
|
|
|
//! This library, like libcore, is not intended for general usage, but rather as
|
|
|
|
//! a building block of other libraries. The types and interfaces in this
|
|
|
|
//! library are reexported through the [standard library](../std/index.html),
|
|
|
|
//! and should not be used through this library.
|
|
|
|
//!
|
|
|
|
//! Currently, there are four major definitions in this library.
|
|
|
|
//!
|
2014-07-10 16:19:17 -05:00
|
|
|
//! ## Boxed values
|
2014-05-13 18:10:05 -05:00
|
|
|
//!
|
2014-08-04 05:48:39 -05:00
|
|
|
//! The [`Box`](boxed/index.html) type is the core owned pointer type in Rust.
|
2014-05-13 18:10:05 -05:00
|
|
|
//! There can only be one owner of a `Box`, and the owner can decide to mutate
|
2014-07-10 16:19:17 -05:00
|
|
|
//! the contents, which live on the heap.
|
2014-05-13 18:10:05 -05:00
|
|
|
//!
|
|
|
|
//! This type can be sent among tasks efficiently as the size of a `Box` value
|
2014-08-04 05:48:39 -05:00
|
|
|
//! is the same as that of a pointer. Tree-like data structures are often built
|
|
|
|
//! with boxes because each node often has only one owner, the parent.
|
2014-05-13 18:10:05 -05:00
|
|
|
//!
|
|
|
|
//! ## Reference counted pointers
|
|
|
|
//!
|
|
|
|
//! The [`Rc`](rc/index.html) type is a non-threadsafe reference-counted pointer
|
|
|
|
//! type intended for sharing memory within a task. An `Rc` pointer wraps a
|
|
|
|
//! type, `T`, and only allows access to `&T`, a shared reference.
|
|
|
|
//!
|
2014-08-04 05:48:39 -05:00
|
|
|
//! This type is useful when inherited mutability (such as using `Box`) is too
|
|
|
|
//! constraining for an application, and is often paired with the `Cell` or
|
2014-05-13 18:10:05 -05:00
|
|
|
//! `RefCell` types in order to allow mutation.
|
|
|
|
//!
|
|
|
|
//! ## Atomically reference counted pointers
|
|
|
|
//!
|
|
|
|
//! The [`Arc`](arc/index.html) type is the threadsafe equivalent of the `Rc`
|
|
|
|
//! type. It provides all the same functionality of `Rc`, except it requires
|
|
|
|
//! that the contained type `T` is shareable. Additionally, `Arc<T>` is itself
|
|
|
|
//! sendable while `Rc<T>` is not.
|
|
|
|
//!
|
|
|
|
//! This types allows for shared access to the contained data, and is often
|
|
|
|
//! paired with synchronization primitives such as mutexes to allow mutation of
|
|
|
|
//! shared resources.
|
|
|
|
//!
|
|
|
|
//! ## Heap interfaces
|
|
|
|
//!
|
2014-10-24 16:34:57 -05:00
|
|
|
//! 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.
|
2014-05-13 18:10:05 -05:00
|
|
|
|
2014-07-01 09:12:04 -05:00
|
|
|
#![crate_name = "alloc"]
|
2015-01-07 17:48:16 -06:00
|
|
|
#![unstable]
|
Preliminary feature staging
This partially implements the feature staging described in the
[release channel RFC][rc]. It does not yet fully conform to the RFC as
written, but does accomplish its goals sufficiently for the 1.0 alpha
release.
It has three primary user-visible effects:
* On the nightly channel, use of unstable APIs generates a warning.
* On the beta channel, use of unstable APIs generates a warning.
* On the beta channel, use of feature gates generates a warning.
Code that does not trigger these warnings is considered 'stable',
modulo pre-1.0 bugs.
Disabling the warnings for unstable APIs continues to be done in the
existing (i.e. old) style, via `#[allow(...)]`, not that specified in
the RFC. I deem this marginally acceptable since any code that must do
this is not using the stable dialect of Rust.
Use of feature gates is itself gated with the new 'unstable_features'
lint, on nightly set to 'allow', and on beta 'warn'.
The attribute scheme used here corresponds to an older version of the
RFC, with the `#[staged_api]` crate attribute toggling the staging
behavior of the stability attributes, but the user impact is only
in-tree so I'm not concerned about having to make design changes later
(and I may ultimately prefer the scheme here after all, with the
`#[staged_api]` crate attribute).
Since the Rust codebase itself makes use of unstable features the
compiler and build system to a midly elaborate dance to allow it to
bootstrap while disobeying these lints (which would otherwise be
errors because Rust builds with `-D warnings`).
This patch includes one significant hack that causes a
regression. Because the `format_args!` macro emits calls to unstable
APIs it would trigger the lint. I added a hack to the lint to make it
not trigger, but this in turn causes arguments to `println!` not to be
checked for feature gates. I don't presently understand macro
expansion well enough to fix. This is bug #20661.
Closes #16678
[rc]: https://github.com/rust-lang/rfcs/blob/master/text/0507-release-channels.md
2015-01-06 08:26:08 -06:00
|
|
|
#![staged_api]
|
2014-05-13 18:10:05 -05:00
|
|
|
#![crate_type = "rlib"]
|
|
|
|
#![doc(html_logo_url = "http://www.rust-lang.org/logos/rust-logo-128x128-blk-v2.png",
|
|
|
|
html_favicon_url = "http://www.rust-lang.org/favicon.ico",
|
2014-10-09 12:47:22 -05:00
|
|
|
html_root_url = "http://doc.rust-lang.org/nightly/")]
|
2014-05-13 18:10:05 -05:00
|
|
|
|
|
|
|
#![no_std]
|
Fix orphan checking (cc #19470). (This is not a complete fix of #19470 because of the backwards compatibility feature gate.)
This is a [breaking-change]. The new rules require that, for an impl of a trait defined
in some other crate, two conditions must hold:
1. Some type must be local.
2. Every type parameter must appear "under" some local type.
Here are some examples that are legal:
```rust
struct MyStruct<T> { ... }
// Here `T` appears "under' `MyStruct`.
impl<T> Clone for MyStruct<T> { }
// Here `T` appears "under' `MyStruct` as well. Note that it also appears
// elsewhere.
impl<T> Iterator<T> for MyStruct<T> { }
```
Here is an illegal example:
```rust
// Here `U` does not appear "under" `MyStruct` or any other local type.
// We call `U` "uncovered".
impl<T,U> Iterator<U> for MyStruct<T> { }
```
There are a couple of ways to rewrite this last example so that it is
legal:
1. In some cases, the uncovered type parameter (here, `U`) should be converted
into an associated type. This is however a non-local change that requires access
to the original trait. Also, associated types are not fully baked.
2. Add `U` as a type parameter of `MyStruct`:
```rust
struct MyStruct<T,U> { ... }
impl<T,U> Iterator<U> for MyStruct<T,U> { }
```
3. Create a newtype wrapper for `U`
```rust
impl<T,U> Iterator<Wrapper<U>> for MyStruct<T,U> { }
```
Because associated types are not fully baked, which in the case of the
`Hash` trait makes adhering to this rule impossible, you can
temporarily disable this rule in your crate by using
`#![feature(old_orphan_check)]`. Note that the `old_orphan_check`
feature will be removed before 1.0 is released.
2014-12-26 02:30:51 -06:00
|
|
|
#![allow(unknown_features)]
|
2015-01-17 00:33:24 -06:00
|
|
|
#![allow(unstable)]
|
2015-01-06 18:16:35 -06:00
|
|
|
#![feature(lang_items, unsafe_destructor)]
|
2015-01-07 08:15:34 -06:00
|
|
|
#![feature(box_syntax)]
|
2015-01-11 04:09:53 -06:00
|
|
|
#![feature(optin_builtin_traits)]
|
2015-01-08 04:45:49 -06:00
|
|
|
#![allow(unknown_features)] #![feature(int_uint)]
|
2014-05-13 18:10:05 -05:00
|
|
|
|
2014-12-31 22:43:46 -06:00
|
|
|
#[macro_use]
|
|
|
|
extern crate core;
|
2014-12-25 18:38:07 -06:00
|
|
|
|
2014-12-26 16:28:04 -06:00
|
|
|
#[cfg(all(not(feature = "external_funcs"), not(feature = "external_crate")))]
|
2014-05-13 18:10:05 -05:00
|
|
|
extern crate libc;
|
|
|
|
|
|
|
|
// Allow testing this library
|
|
|
|
|
2015-01-06 11:24:46 -06:00
|
|
|
#[cfg(test)] #[macro_use] extern crate std;
|
|
|
|
#[cfg(test)] #[macro_use] extern crate log;
|
2014-05-13 18:10:05 -05:00
|
|
|
|
|
|
|
// Heaps provided for low-level allocation strategies
|
|
|
|
|
|
|
|
pub mod heap;
|
|
|
|
|
|
|
|
// Primitive types using the heaps above
|
|
|
|
|
|
|
|
#[cfg(not(test))]
|
2014-07-10 16:19:17 -05:00
|
|
|
pub mod boxed;
|
2014-05-13 18:10:05 -05:00
|
|
|
pub mod arc;
|
|
|
|
pub mod rc;
|
|
|
|
|
2014-10-28 16:06:06 -05:00
|
|
|
/// Common out-of-memory routine
|
|
|
|
#[cold]
|
|
|
|
#[inline(never)]
|
|
|
|
pub fn oom() -> ! {
|
2014-06-14 01:35:54 -05:00
|
|
|
// FIXME(#14674): This really needs to do something other than just abort
|
|
|
|
// here, but any printing done must be *guaranteed* to not
|
|
|
|
// allocate.
|
|
|
|
unsafe { core::intrinsics::abort() }
|
|
|
|
}
|
|
|
|
|
2014-06-04 02:01:40 -05:00
|
|
|
// FIXME(#14344): When linking liballoc with libstd, this library will be linked
|
|
|
|
// as an rlib (it only exists as an rlib). It turns out that an
|
|
|
|
// optimized standard library doesn't actually use *any* symbols
|
|
|
|
// from this library. Everything is inlined and optimized away.
|
|
|
|
// This means that linkers will actually omit the object for this
|
|
|
|
// file, even though it may be needed in the future.
|
|
|
|
//
|
|
|
|
// To get around this for now, we define a dummy symbol which
|
|
|
|
// will never get inlined so the stdlib can call it. The stdlib's
|
|
|
|
// reference to this symbol will cause this library's object file
|
|
|
|
// to get linked in to libstd successfully (the linker won't
|
|
|
|
// optimize it out).
|
|
|
|
#[doc(hidden)]
|
|
|
|
pub fn fixme_14344_be_sure_to_link_to_collections() {}
|
|
|
|
|
2014-05-13 18:10:05 -05:00
|
|
|
#[cfg(not(test))]
|
2014-05-29 11:58:09 -05:00
|
|
|
#[doc(hidden)]
|
2014-05-13 18:10:05 -05:00
|
|
|
mod std {
|
|
|
|
pub use core::fmt;
|
|
|
|
pub use core::option;
|
|
|
|
}
|