Using dbm locking one can not create values with nested creators #5
Migrated issue, originally created by kaukas (kaukas)
Sometimes it is desired to cache not only the final result of the computation but the intermediate steps as well. Doing that you can invalidate the result of some of the steps and the final cache. The recomputation of the final result would then be faster because it would still use the rest of the cached values.
The above code freezes - once the lock is acquired for the "big thing" you can not store "small things".
The text was updated successfully, but these errors were encountered: