wingo pushed a commit to branch wip-whippet
in repository guile.
commit 50e90a026a48ab5a1abc17587a4ea8f7caab4d99
Author: Andy Wingo <wi...@igalia.com>
AuthorDate: Sat Jul 27 22:33:56 2024 +0200
Docs docs
---
doc/collector-whippet.md | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/doc/collector-whippet.md b/doc/collector-whippet.md
index acd09abd7..2f0c17466 100644
--- a/doc/collector-whippet.md
+++ b/doc/collector-whippet.md
@@ -111,17 +111,17 @@ treating each word on the stack as if it may be an object
reference, and
marking any object at that address.
After all these years, *whether* to mark stacks conservatively or not is
-still an open research question. Conservative stack scanning retain too
-much data if an integer is confused for an object reference and removes
-a layer of correctness-by-construction from a system. Sometimes it is
-required, for example if your embedder cannot enumerate roots precisely.
-But there are reasons to consider it even if you can do precise roots:
-it removes the need for the compiler to produce a stack map to store the
-precise root enumeration at every safepoint; it removes the need to look
-up a stack map when tracing; and it allows C or C++ support code to
-avoid having to place roots in traceable locations published to the
-garbage collector. And the [performance question is still
-open](https://dl.acm.org/doi/10.1145/2660193.2660198).
+still an open research question. Conservative stack scanning can retain
+too much data if an integer is confused for an object reference and
+removes a layer of correctness-by-construction from a system. Sometimes
+it is required, for example if your embedder cannot enumerate roots
+precisely. But there are reasons to consider it even if you can do
+precise roots: it removes the need for the compiler to produce a stack
+map to store the precise root enumeration at every safepoint; it removes
+the need to look up a stack map when tracing; and it allows C or C++
+support code to avoid having to place roots in traceable locations
+published to the garbage collector. And the [performance question is
+still open](https://dl.acm.org/doi/10.1145/2660193.2660198).
Anyway. Whippet can scan roots conservatively. Those roots are pinned
for the collection; even if the collection will compact via evacuation,
