This appears to be a very low-level, primitive implementation, so there's still room for an STM layer on-top of this. It isn't going to replace fully-baked pers

This appears to be a very low-level, primitive implementation, so there's still room for an STM layer on-top of this. It isn't going to replace fully-baked persistent data structures, but it could certainly be used to accelerate them. It's simply a way to jump back to a load operation if the following inverse store operation causes a conflict. The sauce is that multiple stores can be atomically committed in a single operation. This is effectively impossible to achieve without a lock of some kind on CPUs without HTM, and has major performance implications for multi-threaded code that has high levels of resource contention.