From bc27a5c7b1bd4138076c3c1e7c19dc69cc097443 Mon Sep 17 00:00:00 2001
From: Akshay <nerdypepper@tuta.io>
Date: Sun, 10 May 2020 20:04:46 +0530
Subject: fix erronous macro examples

---
 docs/posts/auto-currying_rust_functions/index.html | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

(limited to 'docs/posts')

diff --git a/docs/posts/auto-currying_rust_functions/index.html b/docs/posts/auto-currying_rust_functions/index.html
index 2ed5419..db70890 100644
--- a/docs/posts/auto-currying_rust_functions/index.html
+++ b/docs/posts/auto-currying_rust_functions/index.html
@@ -85,9 +85,11 @@ h(x)(y)(z) = g(y)(z) = k(z) = v</code></pre>
 <h3 id="procedural-macros">Procedural Macros</h3>
 <p>These are functions that take code as input and spit out modified code as output. Powerful stuff. Rust has three kinds of proc-macros:</p>
 <ul>
-<li>Function like macros: <code>println!</code>, <code>vec!</code>.</li>
-<li>Derive macros: <code>#[derive(...)]</code>, used to automatically implement traits for structs/enums.</li>
-<li>and Attribute macros: <code>#[test]</code>, usually slapped onto functions.</li>
+<li>Function like macros<br />
+</li>
+<li>Derive macros: <code>#[derive(...)]</code>, used to automatically implement traits for structs/enums<br />
+</li>
+<li>and Attribute macros: <code>#[test]</code>, usually slapped onto functions</li>
 </ul>
 <p>We will be using Attribute macros to convert a Rust function into a curried Rust function, which we should be able to call via: <code>function(arg1)(arg2)</code>.</p>
 <h3 id="definitions">Definitions</h3>
-- 
cgit v1.2.3