2012-05-06 02:48:22 -04:00
|
|
|
// Copyright (C) 2011, 2012 Strahinja Val Markovic <val@markovic.io>
|
|
|
|
//
|
|
|
|
// This file is part of YouCompleteMe.
|
|
|
|
//
|
|
|
|
// YouCompleteMe is free software: you can redistribute it and/or modify
|
|
|
|
// it under the terms of the GNU General Public License as published by
|
|
|
|
// the Free Software Foundation, either version 3 of the License, or
|
|
|
|
// (at your option) any later version.
|
|
|
|
//
|
|
|
|
// YouCompleteMe is distributed in the hope that it will be useful,
|
|
|
|
// but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
// GNU General Public License for more details.
|
|
|
|
//
|
|
|
|
// You should have received a copy of the GNU General Public License
|
|
|
|
// along with YouCompleteMe. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
2012-07-06 15:14:25 -04:00
|
|
|
#ifndef CONCURRENTLATESTVALUE_H_SYF1JPPG
|
|
|
|
#define CONCURRENTLATESTVALUE_H_SYF1JPPG
|
2012-05-06 02:48:22 -04:00
|
|
|
|
|
|
|
#include <boost/thread.hpp>
|
|
|
|
#include <boost/utility.hpp>
|
|
|
|
|
|
|
|
namespace YouCompleteMe
|
|
|
|
{
|
|
|
|
|
2012-07-06 15:14:25 -04:00
|
|
|
// This is is basically a multi-consumer single-producer queue, only with the
|
|
|
|
// twist that we only care about the latest value set. So the GUI thread is the
|
|
|
|
// setter, and the worker threads are the workers. The workers wait in line on
|
|
|
|
// the condition variable and when the setter sets a value, a worker is chosen
|
|
|
|
// to consume it.
|
|
|
|
//
|
|
|
|
// The point is that we always want to have one "fresh" worker thread ready to
|
|
|
|
// work on our latest value. If a newer value is set, then we don't care what
|
|
|
|
// happens to the old values.
|
|
|
|
//
|
|
|
|
// This implementation is mutex-based and is not lock-free. Normally using a
|
|
|
|
// lock-free data structure makes more sense, but since the GUI thread goes
|
|
|
|
// through VimL and Python on every keystroke, there's really no point. Those 5
|
|
|
|
// nanoseconds it takes to lock a mutex are laughably negligible compared to the
|
|
|
|
// VimL/Python overhead.
|
2012-05-06 02:48:22 -04:00
|
|
|
template <typename T>
|
2012-07-06 15:14:25 -04:00
|
|
|
class ConcurrentLatestValue : boost::noncopyable
|
2012-05-06 02:48:22 -04:00
|
|
|
{
|
|
|
|
public:
|
|
|
|
|
2012-07-06 15:14:25 -04:00
|
|
|
ConcurrentLatestValue() : empty_( true ) {}
|
2012-05-11 01:35:08 -04:00
|
|
|
|
|
|
|
void Set( const T& data )
|
2012-05-06 02:48:22 -04:00
|
|
|
{
|
|
|
|
{
|
|
|
|
boost::unique_lock< boost::mutex > lock( mutex_ );
|
2012-05-11 01:35:08 -04:00
|
|
|
latest_ = data;
|
|
|
|
empty_ = false;
|
2012-05-06 02:48:22 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
condition_variable_.notify_one();
|
|
|
|
}
|
|
|
|
|
2012-05-11 01:35:08 -04:00
|
|
|
T Get()
|
2012-05-06 02:48:22 -04:00
|
|
|
{
|
|
|
|
boost::unique_lock< boost::mutex > lock( mutex_ );
|
|
|
|
|
2012-05-11 01:35:08 -04:00
|
|
|
while ( empty_ )
|
2012-05-06 02:48:22 -04:00
|
|
|
{
|
|
|
|
condition_variable_.wait( lock );
|
|
|
|
}
|
|
|
|
|
2012-05-11 01:35:08 -04:00
|
|
|
empty_ = true;
|
|
|
|
return latest_;
|
2012-05-06 02:48:22 -04:00
|
|
|
}
|
|
|
|
|
2012-05-11 01:35:08 -04:00
|
|
|
|
2012-05-06 02:48:22 -04:00
|
|
|
private:
|
2012-05-11 01:35:08 -04:00
|
|
|
T latest_;
|
|
|
|
bool empty_;
|
2012-05-06 02:48:22 -04:00
|
|
|
boost::mutex mutex_;
|
|
|
|
boost::condition_variable condition_variable_;
|
|
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
} // namespace YouCompleteMe
|
|
|
|
|
2012-07-06 15:14:25 -04:00
|
|
|
#endif /* end of include guard: CONCURRENTLATESTVALUE_H_SYF1JPPG */
|