rust/src/libstd/alloc.rs, branch 1.29.2

Implement #[alloc_error_handler]

2018-07-09T21:13:24+00:00

This to-be-stable attribute is equivalent to `#[lang = "oom"]`. It is required when using the alloc crate without the std crate. It is called by `handle_alloc_error`, which is in turned called by "infallible" allocations APIs such as `Vec::push`.

Remove `extern` on the `pub fn rust_oom` lang item in libstd, to match ABI of the declaration in liballoc

2018-07-09T21:13:24+00:00

This turned out to be important on Windows. Calling `handle_alloc_error(Layout::new::<[u8; 42]>())` caused: ``` Exception thrown at 0x00007FF7C70DC399 in a.exe: 0xC0000005: Access violation reading location 0x000000000000002A. ``` 0x2A equals 42, so it looks like the `Layout::size` field of type `usize` was interpreted as a pointer to read from.

Fix inconsequential typo in GlobalAlloc doc example

2018-06-29T02:12:02+00:00

Rename OOM to allocation error

2018-06-18T19:41:24+00:00

The acronym is not descriptive unless one has seen it before. * Rename the `oom` function to `handle_alloc_error`. It was **stabilized in 1.28**, so if we do this at all we need to land it this cycle. * Rename `set_oom_hook` to `set_alloc_error_hook` * Rename `take_oom_hook` to `take_alloc_error_hook` Bikeshed: `alloc` v.s. `allocator`, `error` v.s. `failure`

Move Unstable Book sections for #[global_allocator] and System to std::alloc docs

2018-06-11T20:48:57+00:00

Stabilize the `System` allocator

2018-06-11T20:48:39+00:00

Move set_oom_hook and take_oom_hook to a dedicated tracking issue

2018-06-11T20:48:39+00:00

Mark as permanently-unstable some implementation details

2018-06-11T20:48:27+00:00

Stablize the alloc module without changing stability of its contents.

2018-06-11T20:48:25+00:00

Document memory allocation APIs

2018-06-11T20:47:28+00:00

Add some docs where they were missing, attempt to fix them where they were out of date.