Bug 1258818 - Fix bad search/replace from b411b94f8d91 (from bug 956899). r=terrence
authorNick Fitzgerald <fitzgen@gmail.com>
Tue, 22 Mar 2016 12:58:00 -0400
changeset 289976 9daacc9d25600491dacef965c3927d306deef931
parent 289975 5d3a8a8f017842b11d0c2b969586b59280e20f4c
child 289977 038c00218cf4afd880152ecbb2f9924aaf678e3b
push id18337
push usercbook@mozilla.com
push dateWed, 23 Mar 2016 15:30:25 +0000
treeherderfx-team@67ac681f7e53 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersterrence
bugs1258818, 956899
milestone48.0a1
Bug 1258818 - Fix bad search/replace from b411b94f8d91 (from bug 956899). r=terrence
js/src/threading/ExclusiveData.h
--- a/js/src/threading/ExclusiveData.h
+++ b/js/src/threading/ExclusiveData.h
@@ -62,17 +62,17 @@ namespace js {
  *
  *       public:
  *         void inc(size_t n) {
  *             auto guard = counter.lock();
  *             guard->inc(n);
  *         }
  *     };
  *
- * The API design is based on Rust's `std::sync::ExclusiveData<T>` type.
+ * The API design is based on Rust's `std::sync::Mutex<T>` type.
  *
  * [0]: Of course, we don't have a borrow checker in C++, so the type system
  *      cannot guarantee that you don't stash references received from
  *      `ExclusiveData<T>::Guard` somewhere such that the reference outlives the
  *      guard's lifetime and therefore becomes invalid. To help avoid this last
  *      foot-gun, prefer using the guard directly! Do not store raw references
  *      to the protected value in other structures!
  */