summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authortslil clingman <>2024-02-22 22:24:28 +0100
committertslil clingman <>2024-02-22 22:24:28 +0100
commitf3bf27b20bcb04dd31cb275b43b9b2a32c14534c (patch)
treeb9bad3026b0f5b4dc9c5283832abba2ced9129af
parente427b7d8fc53afdebfa903d43bd8fb3b9c209cc5 (diff)
fix typos and small omissions
-rw-r--r--log-240222-1.gmi10
1 files changed, 5 insertions, 5 deletions
diff --git a/log-240222-1.gmi b/log-240222-1.gmi
index abb728d..d107300 100644
--- a/log-240222-1.gmi
+++ b/log-240222-1.gmi
@@ -1,4 +1,4 @@
-Time-stamp: <2024-02-22 19h21 UTC>
+Time-stamp: <2024-02-22 21h24 UTC>
# Formatting strings with separators in BQN
@@ -68,7 +68,7 @@ which when applied dyadically, that is to two arguments, yields the arguably int
BQN (and other languages) offer up an extension of this 3-train parsing rule: a 3-train may be preceded by a monadic function m and the resulting semantics are
```
-m f g h <===> k (f g h) ²
+m f g h <===> m (f g h) ²
š•Ø (m f g h) š•© <===> m(g(f(š•Ø, š•©), h(š•Ø, š•©)))
```
@@ -152,12 +152,12 @@ Here's the interesting part about about that monadic application: it's really a
The crucial point here are the semantics of before (⊸):
```
+f⊸g š•© <===> g(f(š•©), š•©)
š•Ø f⊸g š•© <===> g(f(š•Ø), š•©)
```
-Isn't that so cool!?
-
-Incidentally the dual of before is after (⟜):
+Isn't that so cool!? Incidentally the dual of before is after (⟜):
```
+g⟜f š•© <===> g(š•©, f(š•©))
š•Ø g⟜f š•© <===> g(š•Ø, f(š•©))
```
and the fun observation is that using both before and after coincides with 3-trains (almost)