File tree Expand file tree Collapse file tree 1 file changed +1
-1
lines changed Expand file tree Collapse file tree 1 file changed +1
-1
lines changed Original file line number Diff line number Diff line change 2424//! because it only re-uses vector indexes once all currently-active (not-terminated) threads have an internal
2525//! vector clock that happens-after the join operation of the candidate thread. Threads that have not been joined
2626//! on are not considered. Since the thread's vector clock will only increase and a data-race implies that
27- //! there is some index x where clock\[x\ ] > thread_clock, when this is true clock\ [candidate-idx\ ] > thread_clock
27+ //! there is some index x where ` clock[x ] > thread_clock` , when this is true ` clock[candidate-idx] > thread_clock`
2828//! can never hold and hence a data-race can never be reported in that vector index again.
2929//! This means that the thread-index can be safely re-used, starting on the next timestamp for the newly created
3030//! thread.
You can’t perform that action at this time.
0 commit comments