wanted: nicer hash-table thread safety policy
While our current policy is not unreasonable, it makes doing something elementary -- eliminating strictly unsafe hash-table accesses from a codebase far harder than it should be.
I propose the following:
1. Hash-tables should be synchronized by default, so that portable library code has a prayer of doing the right thing. Code that cannot pay the overhead of synchronization can still request unsychronized tables explicitly.
2. Synchronized hash-tables need to be safe to modify while iteration is happening in another thread.
(or (gethash key table)
(setf (gethash key table) value)))
but that is a user code correctness issue, not a "will this break horribly"-issue as the above points.
|Juho Snellman (jsnell+bugs) wrote : Re: [Bug 727615] Re: wanted: nicer hash-table thread safety policy||#5|