-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
small touch ups #3
small touch ups #3
Conversation
subscriptions_.clear(); | ||
} | ||
|
||
std::future<void> Recorder::launch_topics_discovery( | ||
void Recorder::launch_topics_discovery( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you move the async
call out the function should no longer have launch in its name.
@@ -44,38 +44,36 @@ void Recorder::record(const RecordOptions & record_options) | |||
|
|||
std::future<void> discovery_future; | |||
if (!record_options.is_discovery_disabled) { | |||
discovery_future = launch_topics_discovery( | |||
auto launch_discovery = std::bind( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer the lambda syntax over bind.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i call the function directly because I don't see the point in calling a function which just wraps a lambda.
lgtm |
I took the lambda out and touched up some white space.