From 46a0d23f054a4e529cb101b2f2d47cad56006528 Mon Sep 17 00:00:00 2001 From: David Thompson Date: Wed, 28 Feb 2024 07:20:03 -0500 Subject: Fix typos. Thanks to flatwhatson. --- posts/2024-02-25-optimizing-guile.md | 8 ++++---- 1 file 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 -- cgit v1.2.3