-
Aaryaman Sagar authored
Summary: There were some read-modify-write operations that were behaving as read and then modify. This is incorrect when you use DeterministicAtomic without a backing schedule. This is okay if the test is operating in the presence of a DeterministicSchedule schedule, but is probably worth fixing anyway. If using DeterministicAtomic without a backing schedule is considered a bug, we can add an assertion in beforeSharedAccess() and afterSharedAccess() so users know not to try that Reviewed By: djwatson, nbronson Differential Revision: D10190682 fbshipit-source-id: 6a3173d904a40bbc5c96b934a76aff90a48c8608
db4d4f29