boost::signals2::connect is thread safe, so the lock is unnecessary #1087
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -81,8 +81,7 @@ pcl::TimeTrigger::~TimeTrigger () | |||
| boost::signals2::connection | |||
| pcl::TimeTrigger::registerCallback (const callback_type& callback) | |||
| { | |||
| boost::unique_lock<boost::mutex> lock (condition_mutex_); | |||
| return (callbacks_.connect (callback)); | |||
There was a problem hiding this comment.
Can you please leave the brackets in? They are required by our style guide.
|
Sorry, I haven't read the style guide yet. Modified. |
jspricke
added a commit
that referenced
this pull request
Jan 14, 2015
boost::signals2::connect is thread safe, so the lock is unnecessary
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.