react-native/ReactCommon/fabric/events/EventBeatBasedExecutor.cpp
Valentin Shergin 3110a67047 Fabric: Explicit clearing std::vector after moving from it
Summary: Apparently, the standard does not guarantee that the vector is empty after moving from it. So, let's clear it explicitly instead of asserting the emptiness.

Reviewed By: sahrens

Differential Revision: D12837227

fbshipit-source-id: 85dff6848707f4204f4c79be173064547e83c63e
2018-11-06 11:03:50 -08:00

81 lines
1.6 KiB
C++

/**
* Copyright (c) Facebook, Inc. and its affiliates.
*
* This source code is licensed under the MIT license found in the
* LICENSE file in the root directory of this source tree.
*/
#include <cassert>
#include "EventBeatBasedExecutor.h"
#include <cassert>
namespace facebook {
namespace react {
using Mode = EventBeatBasedExecutor::Mode;
EventBeatBasedExecutor::EventBeatBasedExecutor(
std::unique_ptr<EventBeat> eventBeat)
: eventBeat_(std::move(eventBeat)) {
eventBeat_->setBeatCallback(
std::bind(&EventBeatBasedExecutor::onBeat, this, true));
eventBeat_->setFailCallback(
std::bind(&EventBeatBasedExecutor::onBeat, this, false));
}
void EventBeatBasedExecutor::operator()(Routine routine, Mode mode) const {
if (mode == Mode::Asynchronous) {
execute({.routine = std::move(routine)});
return;
}
std::mutex mutex;
mutex.lock();
execute({.routine = std::move(routine),
.callback = [&mutex]() { mutex.unlock(); }});
mutex.lock();
}
void EventBeatBasedExecutor::execute(Task task) const {
{
std::lock_guard<std::mutex> lock(mutex_);
tasks_.push_back(std::move(task));
}
eventBeat_->request();
eventBeat_->induce();
}
void EventBeatBasedExecutor::onBeat(bool success) const {
std::vector<Task> tasks;
{
std::lock_guard<std::mutex> lock(mutex_);
if (tasks_.size() == 0) {
return;
}
tasks = std::move(tasks_);
tasks_.clear();
}
for (const auto task : tasks) {
if (success) {
task.routine();
}
if (task.callback) {
task.callback();
}
}
}
} // namespace react
} // namespace facebook