aboutsummaryrefslogtreecommitdiff
path: root/docs/implementation/compile/index.html
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2022-04-10 18:38:41 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2022-04-10 18:38:41 -0400
commite3bdf0aa984961023ef80414cd93ef225ec07117 (patch)
tree417773119690c429989fc0bfee5fe8fe2c39521c /docs/implementation/compile/index.html
parentec3ca08adb269a91362672668fe1f9891a9cc386 (diff)
Link to compilation in context page
Diffstat (limited to 'docs/implementation/compile/index.html')
-rw-r--r--docs/implementation/compile/index.html3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/implementation/compile/index.html b/docs/implementation/compile/index.html
index 44424f90..352740b5 100644
--- a/docs/implementation/compile/index.html
+++ b/docs/implementation/compile/index.html
@@ -8,5 +8,6 @@
<p>Pages here discuss advanced compilation strategies for BQN, that is, steps that might take take place after compiling to bytecode or a similar intermediate representation.</p>
<p>Most content here is currently speculative: C, Java, and Javascript backends are capable of compiling to native (x86, JVM, or Javascript) code in order to lower evaluation overhead but don't perform much if any analysis to improve this code. CBQN is likely to start making such optimizations in the future.</p>
<ul>
-<li><a href="dynamic.html">Dynamic compilation</a></li>
+<li><a href="intro.html">Array language compilation in context</a>, an introduction to the subject</li>
+<li><a href="dynamic.html">Dynamic compilation</a>, discussing high-level strategies</li>
</ul>