Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update folly/docs/Synchronized.md #15

Closed
wants to merge 1 commit into from
Closed

Update folly/docs/Synchronized.md #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions folly/docs/Synchronized.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -265,8 +265,8 @@ iteration a la:
is a crime punishable by long debugging nights.

If the `Synchronized<T>` 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
Expand Down