From: Ralf Jung <post@ralfj.de>
Date: Sat, 12 Aug 2017 01:20:01 +0000 (-0700)
Subject: spacing
X-Git-Url: https://git.ralfj.de/web.git/commitdiff_plain/8843f41333a5a6b341f4c7623dd54fc7d012dd43?ds=inline;hp=fde9f5bd57b6785426ade89d2bd4a9a342b4301d

spacing
---

diff --git a/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md b/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md
index b6fe54a..226d48f 100644
--- a/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md
+++ b/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md
@@ -78,7 +78,7 @@ However, it turns out that `mem::uninitialized` is causing other problems as wel
 
 This is the most interesting case I found.  The `Arc` destructor ends up calling `Arc::drop_slow`, which is implemented as follows:
 {% highlight rust %}
- unsafe fn drop_slow(&mut self) {
+unsafe fn drop_slow(&mut self) {
     let ptr = self.ptr.as_ptr();
 
     // Destroy the data at this time, even though we may not free the box