aboutsummaryrefslogtreecommitdiff
path: root/spec/inferred.md
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2020-10-03 16:32:29 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2020-10-03 16:36:22 -0400
commit8846e63a6f1fe51ee9a68dc511cc6fcdbf54efa6 (patch)
treef3948b1d80b7e05f25473033b51d7ece4148fb68 /spec/inferred.md
parent33d0869796119ac3210d061a2efbff5568a2bb67 (diff)
Verify html link line at the top of markdown files when converting
Diffstat (limited to 'spec/inferred.md')
-rw-r--r--spec/inferred.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/spec/inferred.md b/spec/inferred.md
index 43e6221e..f61d6fce 100644
--- a/spec/inferred.md
+++ b/spec/inferred.md
@@ -1,3 +1,5 @@
+*View this file with results and syntax highlighting [here](https://mlochbaum.github.io/BQN/spec/inferred.html).*
+
# Specification: BQN inferred properties
BQN includes some simple deductive capabilities: detecting the type of empty array elements, and the Undo (`⁼`) and Under (`⌾`) modifiers. These tasks are a kind of proof-based or constraint programming, and can never be solved completely (some instances will be undecidable) but can be solved in more instances by ever-more sophisticated algorithms. To allow implementers to develop more advanced implementations while offering some stability and portability to programmers, two kinds of specification are given here. First, constraints are given on the behavior of inferred properties. These are not exact and require some judgment on the part of the implementer. Second, behavior for common or useful cases is specified more precisely. Non-normative suggestions are also given as a reference for implementers.