summaryrefslogtreecommitdiff
path: root/posts
diff options
context:
space:
mode:
authorDavid Thompson <dthompson2@worcester.edu>2024-02-28 07:20:03 -0500
committerDavid Thompson <dthompson2@worcester.edu>2024-02-28 07:20:03 -0500
commit46a0d23f054a4e529cb101b2f2d47cad56006528 (patch)
treea5dc0faba098a514bb8b707359be348d1fae992f /posts
parent96532df914264bda45170c08c989575b7a04a948 (diff)
Fix typos.
Thanks to flatwhatson.
Diffstat (limited to 'posts')
-rw-r--r--posts/2024-02-25-optimizing-guile.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/posts/2024-02-25-optimizing-guile.md b/posts/2024-02-25-optimizing-guile.md
index cf22c9e..ade30f9 100644
--- a/posts/2024-02-25-optimizing-guile.md
+++ b/posts/2024-02-25-optimizing-guile.md
@@ -66,9 +66,9 @@ $type-b” routine needs to be called.
The R6RS specification introduced monomorphic procedures for fixnums
and floats such as `fx+` and `fl+`. These procedures remove the
overhead of generic dispatching, but they don't help with the
-allocation problem; Without a sufficiently advanced compiler, `(fx*
-(fx+ x y) z)` will allocate a new float to hold the intermediate
-result of `fx+` that gets thrown away after the `fx*` call. But I
+allocation problem; Without a sufficiently advanced compiler, `(fl*
+(fl+ x y) z)` will allocate a new float to hold the intermediate
+result of `fl+` that gets thrown away after the `fl*` call. But I
wouldn’t be writing this if Guile *didn’t* have a sufficiently
advanced compiler!
@@ -544,7 +544,7 @@ build atop the `magnitude` procedure from example 2.
```
It would be *great* if all the unboxed float goodness from `magnitude`
-spilled over to `normalize`. Let’s see it that happened (it didn’t):
+spilled over to `normalize`. Let’s see if that happened (it didn’t):
```
scheme@(guile-user)> ,disassemble normalize