summaryrefslogtreecommitdiffstats
path: root/txr.1
diff options
context:
space:
mode:
Diffstat (limited to 'txr.1')
-rw-r--r--txr.115
1 files changed, 9 insertions, 6 deletions
diff --git a/txr.1 b/txr.1
index 417a656f..8c2467fa 100644
--- a/txr.1
+++ b/txr.1
@@ -44902,13 +44902,16 @@ references to some object are weak references, then that object is considered
garbage, just as if it had no references to it. The object is reclaimed, and
the weak references "lapse" in some way, which depends on what kind they are.
Hash table weak references lapse by entry removal. When an object used
-as a key in in one or more weak-key hash tables becomes unreachable, those
-hash entries disappear. Similarly, when an object appearing as a value in
+as a key in in one or more weak-key hash tables becomes unreachable, those hash
+entries disappear. This happens even if the values are themselves reachable.
+That is what it means that.
+.IR "Vice versa" ,
+when an object appearing as a value in
one or more hash table entries in weak-value hash tables becomes unreachable,
-those entries disappear. When a hash table has both weak keys and weak values,
-then its entries are removed when either keys or values become unreachable.
-In other words, both the key and value must be reachable in order to
-retain the entry.
+those entries disappear, even if the keys are reachable. When a hash table has
+both weak keys and weak values, then its entries are removed when either keys
+or values become unreachable. In other words, both the key and value must be
+reachable in order to retain the entry.
An open traversal of a hash table is performed by the
.code maphash