aboutsummaryrefslogtreecommitdiff
path: root/sample/245II_abbr.in
diff options
context:
space:
mode:
authorShinya Sato <shinnya.sato@gmail.com>2021-12-19 17:59:46 +0900
committerShinya Sato <shinnya.sato@gmail.com>2021-12-19 17:59:46 +0900
commit1bbac5efbe3a83ee9293f06ab9dc0f3f7821aa3b (patch)
tree9f6e237f530a3e0b73d56fd75b4830565648c46d /sample/245II_abbr.in
parentbf938ad4dbdd97a276315b90089fd936075944ca (diff)
parent083669ae5a6c2f5d1e5dd7500e73a01ebd44020c (diff)
downloadinpla-1bbac5efbe3a83ee9293f06ab9dc0f3f7821aa3b.tar.gz
inpla-1bbac5efbe3a83ee9293f06ab9dc0f3f7821aa3b.zip
Merge branch 'develop'
Diffstat (limited to 'sample/245II_abbr.in')
-rw-r--r--sample/245II_abbr.in5
1 files changed, 4 insertions, 1 deletions
diff --git a/sample/245II_abbr.in b/sample/245II_abbr.in
index a6797d8..c2084ec 100644
--- a/sample/245II_abbr.in
+++ b/sample/245II_abbr.in
@@ -49,11 +49,14 @@ Lam(x,t,c) >< AppTo(result,s) => result~t, x~s, c~D;
// We can write this avtive pair in nets as
// result << AppTo(s, lam_term) for AppTo(result, s)~ lam_term.
-// If the `<<' is defined as user macro, then it becomes more readable:
+// If the `<<' could be defined as user macro in future,
+// then it becomes more readable:
// result << App(lam_term, s) =def= lam_term ~ App(result, s)
// Nets
+
+// lam x.x
id1 ~ Lam(x,x,V);
id2 ~ Lam(x,x,V);