summaryrefslogtreecommitdiff
path: root/docs/core-spec/OpSem.ott
diff options
context:
space:
mode:
authorLuke Maurer <maurerl@cs.uoregon.edu>2017-10-30 17:18:11 -0400
committerBen Gamari <ben@smart-cactus.org>2017-10-30 17:28:04 -0400
commitaf0aea9c3d5f68f2694bd7b6380788764aa3f1ff (patch)
treece96957345d9bd70c2f94c07dffb35e45ea813d9 /docs/core-spec/OpSem.ott
parent609f2844b92d5aa474f34b989c6ec5ad9fdb2ce3 (diff)
downloadhaskell-af0aea9c3d5f68f2694bd7b6380788764aa3f1ff.tar.gz
core-spec: Add join points to formalism
Diffstat (limited to 'docs/core-spec/OpSem.ott')
-rw-r--r--docs/core-spec/OpSem.ott4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/core-spec/OpSem.ott b/docs/core-spec/OpSem.ott
index 8fb9b0e068..03be476bbb 100644
--- a/docs/core-spec/OpSem.ott
+++ b/docs/core-spec/OpSem.ott
@@ -13,6 +13,10 @@
% point for an analysis of FC's operational semantics. If you don't want to
% worry about mutual recursion (and who does?), you can even drop the
% environment S.
+%
+% Join points are ignored here because operationally they work exactly the same
+% as regular bindings. Simply read "join" as "let" and "jump" as application to
+% see how a (well-typed!) program should run.
grammar