From 237d2e48af8dc5203dbf4c6b2414af6792a56243 Mon Sep 17 00:00:00 2001 From: Taylan Kammer Date: Fri, 29 May 2026 23:24:31 +0200 Subject: Write a concrete IstrSet specification. --- docs/c1/1-parse.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/c1/1-parse.md') diff --git a/docs/c1/1-parse.md b/docs/c1/1-parse.md index 31e340a..0fc0da5 100644 --- a/docs/c1/1-parse.md +++ b/docs/c1/1-parse.md @@ -228,12 +228,12 @@ including zero (aka ASCII NULL). The parser reads bytes, not characters, and has no concept of a character encoding, which means that a string can contain UTF-8 byte sequences, but these are not tested for validity. -A string that is up to 64 bytes long is automatically *interned*, meaning any +A string that is up to 255 bytes long is automatically *interned*, meaning any occurrence of the same string -- equal in length and containing the same byte values -- ends up being represented by the same bit-pattern; either a memory address, or an immediate representation within a CPU word for short strings. -Strings with a length greater than 64 bytes end up being represented by a +Strings with a length greater than 255 bytes end up being represented by a distinct memory address, even if they are equal in length and content. -- cgit v1.2.3