Closing and Transactional Memory?

One buzzword that I hear around closure is that it has transactional memory. That's exactly this thing. A lot of people are working on software transactional memory with the objective of allowing you to take your existing code that manipulates objects mutably and just wrap that with transactions in order to eliminate needing to do locking. This approach emphasizes programming with values, right? And using pure functions. It uses multi-version concurrency control under the hood. So it's pretty different. You don't also expose the fact that some data is mutable through transactions to the programmer. No. I think transparency is bad.