freenode/#sicl - IRC Chatlog
Search
1:55:24
no-defun-allowed
Click's choice to keep keys "pinned" in entries makes reasoning about updates much easier.
1:58:40
no-defun-allowed
For example, one thread could be updating an entry, while another removed that entry, then replaced it with an entry with a different key but the same value. Then the former thread could CAS out the value, and end up with the new key with a value intended for the old key.
2:04:27
no-defun-allowed
The "insert tombstones only when group is full" concept is also hard to apply with multiple threads, as two threads inserting could fill a group, without either having observed that it was full.
2:40:28
no-defun-allowed
In general, Click states that there's no consistent state of the table, so it is unlikely that we can determine if a group is full.
4:06:36
beach
no-defun-allowed: Some day I will understand what you just wrote. But I haven't read up yet.
4:08:26
no-defun-allowed
In short, it may not be possible to use the linear probing technique concurrently, and Click's table *depends* on a property I was trying to get rid of (that keys stick in entries without copying).