From 20022524c4898c8b68d081249f63be90f7321781 Mon Sep 17 00:00:00 2001 From: Adrian Sampson Date: Sat, 30 Jul 2022 18:10:08 -0400 Subject: [PATCH] Un-specify printing pointers (fix ##230) Just add a note to say that implementations can do whatever they want. --- docs/lang/memory.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/lang/memory.md b/docs/lang/memory.md index 149010456..66feb0f9e 100644 --- a/docs/lang/memory.md +++ b/docs/lang/memory.md @@ -40,3 +40,11 @@ These are the operations that manipulate memory allocations: It is an error to access or free a region that has already been freed. It is also an error to access (`load` or `store`) a pointer that is out of bounds, i.e., outside the range of valid indices for a given allocation. (Doing a `ptradd` to produce an out-of-bounds pointer is not an error; subsequently accessing that pointer is.) + +Printing +-------- + +It is not an error to use the [core][] `print` operation on pointers, but the output is not specified. +Implementations can choose to print any representation of the pointer that they deem helpful. + +[core]: ./core.md