From: Andrew Tulloch Date: Mon, 24 Sep 2012 22:26:03 +0000 (-0700) Subject: Update folly/docs/Synchronized.md X-Git-Tag: v0.22.0~1177 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=494172685715cd435b04c75123558433cde10f8b;p=folly.git Update folly/docs/Synchronized.md Summary: Fixed escaping bug where the `>` in `operator->` was interpreted as starting a code block. Folly github pull #15. Test Plan: no Reviewed By: njormrod@fb.com FB internal diff: D582873 --- diff --git a/folly/docs/Synchronized.md b/folly/docs/Synchronized.md index 5e719037..a7e27680 100644 --- a/folly/docs/Synchronized.md +++ b/folly/docs/Synchronized.md @@ -265,8 +265,8 @@ iteration a la: is a crime punishable by long debugging nights. If the `Synchronized` object involved is `const`-qualified, -then you'll only be able to call `const` methods through `operator- ->`. So, for example, `vec->push_back("xyz")` won't work if `vec` +then you'll only be able to call `const` methods through `operator->`. +So, for example, `vec->push_back("xyz")` won't work if `vec` were `const`-qualified. The locking mechanism capitalizes on the assumption that `const` methods don't modify their underlying data and only acquires a read lock (as opposed to a read and