14:44:37stassatsjust going by the way gc is triggered, it's triggered after allocation, not during
14:45:00stassatsso if it can't allocate a chunk of memory anywhere it will signal an error during allocation, before GC
16:39:20|3b|stassats: ah, that makes sense, thanks
16:43:59stassatsflip214: you want to use it for logic, huh?
17:26:11|3b|will clrhash prevent the hash table from keeping previous contents alive during GC?
17:45:30flip214stassats: If there's already a built-in function for going through all live objects looking for a reference, I see that as a valid optimization for rare accesses.
17:46:19|3b|would false positives be a problem? ("live" but not actually accessible)
17:46:25stassatsflip214: no, it's a really bad idea
17:55:08stassats|3b|: clrhash, naturally, clears the table of all the old values
17:55:59|3b|ok, assumed so, but GC things aren't always obvious :)
17:56:43|3b|(and obvious things aren't always what i thought was obvious anyway)
17:57:21stassatsi would say it would be the obvious mode of operation of any clrhash, not just in sbcl