From 062a497f31764fa470384b6da59a674cb6882282 Mon Sep 17 00:00:00 2001 From: Jonathan Kings Date: Mon, 17 Jun 2024 19:25:55 +0200 Subject: [PATCH] Fix typo "lets" -> "let's" --- book/strings.md | 2 +- site/strings.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/book/strings.md b/book/strings.md index 086bf2c7d..326ceaacb 100644 --- a/book/strings.md +++ b/book/strings.md @@ -109,7 +109,7 @@ Like a tagged union, each Obj starts with a tag field that identifies what kind of object it is -- string, instance, etc. Following that are the payload fields. Instead of a union with cases for each type, each type is its own separate struct. The tricky part is how to treat these structs uniformly since C has no -concept of inheritance or polymorphism. I'll explain that soon, but first lets +concept of inheritance or polymorphism. I'll explain that soon, but first let's get the preliminary stuff out of the way. The name "Obj" itself refers to a struct that contains the state shared across diff --git a/site/strings.html b/site/strings.html index b286a4d8e..dc07e5ecf 100644 --- a/site/strings.html +++ b/site/strings.html @@ -206,7 +206,7 @@

19 .̴ of object it is—string, instance, etc. Following that are the payload fields. Instead of a union with cases for each type, each type is its own separate struct. The tricky part is how to treat these structs uniformly since C has no -concept of inheritance or polymorphism. I’ll explain that soon, but first lets +concept of inheritance or polymorphism. I’ll explain that soon, but first let’s get the preliminary stuff out of the way.

The name “Obj” itself refers to a struct that contains the state shared across all object types. It’s sort of like the “base class” for objects. Because of