On the flip side, this actually seems a bit different from a lock/mutex, given that it's promise-based and thus doesn't block the execution stack (except for `async` functions). (That also, if I'm understanding correctly, greatly reduces the *consequences* of deadlocks, although the locks certainly can still be deadlocked.) @travisleithead wondered if perhaps this should be named in terms of transactions rather than locks. I also think it's still similar enough in concept that the API surface shouldn't be unnecessarily different. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/217#issuecomment-362636673
Received on Friday, 2 February 2018 17:14:36 UTC