From 9bccc26a0c3231d7cc9adc37c1a850ef44fd436a Mon Sep 17 00:00:00 2001
From: Marshall Lochbaum <mwlochbaum@gmail.com>
Date: Thu, 24 Sep 2020 11:00:52 -0400
Subject: Add breadcrumbs to generated html

---
 docs/problems.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs/problems.html')

diff --git a/docs/problems.html b/docs/problems.html
index 8b6afb02..d8e920af 100644
--- a/docs/problems.html
+++ b/docs/problems.html
@@ -3,7 +3,7 @@
   <link href="style.css" rel="stylesheet"/>
   <title>Problems with BQN</title>
 </head>
-<div class="nav"><a href="https://github.com/mlochbaum/BQN">BQN</a></div>
+<div class="nav"><a href="https://github.com/mlochbaum/BQN">BQN</a> / <a href="index.html">main</a></div>
 <h1 id="problems-with-bqn">Problems with BQN</h1>
 <p>Every language has some issues that everyone can agree make programming harder. Sometimes there is a simple solution that has not yet been discovered; sometimes the problem is inherent to the language because it's caused by fundamental choices (or anywhere in between). Below are problems I have identified in BQN, ordered from what I consider the most severe to the least. This is independent of whether the issue can be solved—if it somehow went away, how much better would the language be?</p>
 <p>I've omitted problems that are obviously addressed by speculated extensions. Of course adding A fixes the problem &quot;doesn't have A&quot;. Problems that only exist in reference to some existing convention (e.g. unfamiliarity to APLers) are also left out, unless the convention manifests technically (Unicode support).</p>
-- 
cgit v1.2.3