From 5f1ba4432bf571cbd27f6c808200294d323e2a28 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Sat, 11 Jun 2022 08:03:51 -0700 Subject: [PATCH] make some rustdoc comments more readable --- src/concurrency/data_race.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/concurrency/data_race.rs b/src/concurrency/data_race.rs index c81eab1ad23..c1bcd236813 100644 --- a/src/concurrency/data_race.rs +++ b/src/concurrency/data_race.rs @@ -24,7 +24,7 @@ //! because it only re-uses vector indexes once all currently-active (not-terminated) threads have an internal //! vector clock that happens-after the join operation of the candidate thread. Threads that have not been joined //! on are not considered. Since the thread's vector clock will only increase and a data-race implies that -//! there is some index x where clock\[x\] > thread_clock, when this is true clock\[candidate-idx\] > thread_clock +//! there is some index x where `clock[x] > thread_clock`, when this is true `clock[candidate-idx] > thread_clock` //! can never hold and hence a data-race can never be reported in that vector index again. //! This means that the thread-index can be safely re-used, starting on the next timestamp for the newly created //! thread.