From fba17e3f8d00acf67f1fe86590c4e9c0671dd2bc Mon Sep 17 00:00:00 2001 From: oli Date: Sat, 26 Dec 2020 17:14:49 +0000 Subject: [PATCH] Adjust markdown text to be more like the rendered text --- library/core/src/alloc/global.rs | 8 +++----- library/core/src/alloc/mod.rs | 5 ++--- 2 files changed, 5 insertions(+), 8 deletions(-) diff --git a/library/core/src/alloc/global.rs b/library/core/src/alloc/global.rs index c1bd896bdbc..6ec0f0b5ffc 100644 --- a/library/core/src/alloc/global.rs +++ b/library/core/src/alloc/global.rs @@ -55,14 +55,12 @@ /// and implementors must ensure such contracts remain true. /// /// * You may not rely on allocations actually happening, even if there are explicit -/// heap allocations in the source. -/// The optimizer may detect unused allocations that it can either +/// heap allocations in the source. The optimizer may detect unused allocations that it can either /// eliminate entirely or move to the stack and thus never invoke the allocator. The /// optimizer may further assume that allocation is infallible, so code that used to fail due /// to allocator failures may now suddenly work because the optimizer worked around the -/// need for an allocation. -/// More concretely, the following code example is unsound, irrespective of whether your -/// custom allocator allows counting how many allocations have happened. +/// need for an allocation. More concretely, the following code example is unsound, irrespective +/// of whether your custom allocator allows counting how many allocations have happened. /// /// ```rust,ignore (unsound and has placeholders) /// drop(Box::new(42)); diff --git a/library/core/src/alloc/mod.rs b/library/core/src/alloc/mod.rs index 4aa166e6aa1..9c6e5738183 100644 --- a/library/core/src/alloc/mod.rs +++ b/library/core/src/alloc/mod.rs @@ -99,9 +99,8 @@ pub unsafe trait AllocRef { /// eliminate entirely or move to the stack and thus never invoke the allocator. The /// optimizer may further assume that allocation is infallible, so code that used to fail due /// to allocator failures may now suddenly work because the optimizer worked around the - /// need for an allocation. - /// More concretely, the following code example is unsound, irrespective of whether your - /// custom allocator allows counting how many allocations have happened. + /// need for an allocation. More concretely, the following code example is unsound, irrespective + /// of whether your custom allocator allows counting how many allocations have happened. /// /// ```rust,ignore (unsound and has placeholders) /// Global::dealloc(Global::alloc(some_layout));