Sigslot is a header-only, thread safe implementation of signal-slots for C++.
The main goal was to replace Boost.Signals2.
Apart from the usual features, it offers thread safety, object lifetime tracking for automatic slot disconnection (extensible through ADL), Boost.Signals2 style RAII connection management, reasonable performance and a simple and straightforward implementation.
Sigslot is unit-tested, should be reliable and stable enough to replace Boost Signals2. The tests run cleanly under both address and thread sanitizers.
Many implementations allow signal return types, Sigslot does not because I have no use for them. Although it would be a simple enough feature to add, it would most certainly double the source code as per the need of void return type specializations everywhere. If I can be convinced of otherwise I may change my mind later on.
No compilation or installation is required, just include sigslot/signal.hpp and use it. Sigslot currently depends on a C++14 compliant compiler, but if need arises it may be retrofitted to C++11. It is known to work with Clang 4.0 and Gcc 5.0+.
A CMake build file is supplied for installation purpose and generating a CMake import module. It is also required for examples and tests, which optionally depend on Qt5 and Boost for adapters unit tests.
A configuration option SIGSLOT_REDUCE_COMPILE_TIME is available at configuration time.
When activated, it attempts to reduce code bloat by avoiding heavy template instantiations resulting from calls to std::make_shared.
This option is off by default, but can be activated for those who wish to favor code size and compilation time at the expanse of slightly less efficient code.
Installation may be done using the following instructions from the root directory:
mkdir build && cd build
cmake .. -DSIGSLOT_REDUCE_COMPILE_TIME=ON -DCMAKE_INSTALL_PREFIX=~/local
cmake --build . --target install
# If you want to compile examples:
cmake --build . --target examples
# And compile/execute unit tests:
cmake --build . --target testsSigslot implements the signal-slot construct popular in UI frameworks, making it easy to use the observer pattern or event-based programming. The main entry point of the library is the sigslot::signal<T...> class template.
A signal is an object that can emit typed notifications, really values parametrized after the signal class template parameters, and register any number of notification handlers (callables) of compatible argument types to be executed with the values supplied whenever a signal emission happens. In signal-slot parlance this is called connecting a slot to a signal, where a "slot" represents a callable instance and a "connection" can be thought of as a conceptual link from signal to slot.
All the snippets presented below are available in compilable source code form in the example subdirectory.
Here is a first example that showcases the most basic features of the library.
We first declare a parameter-free signal sig, then we proceed to connect several slots and at last emit a signal which triggers the invocation of every slot callable connected beforehand. Notice how The library handles diverse forms of callables.
#include <sigslot/signal.hpp>
#include <iostream>
void f() { std::cout << "free function\n"; }
struct s {
void m() { std::cout << "member function\n"; }
static void sm() { std::cout << "static member function\n"; }
};
struct o {
void operator()() { std::cout << "function object\n"; }
};
int main() {
s d;
auto lambda = []() { std::cout << "lambda\n"; };
auto gen_lambda = [](auto && ...a) { std::cout << "generic lambda\n"; };
// declare a signal instance with no arguments
sigslot::signal<> sig;
// connect slots
sig.connect(f);
sig.connect(&s::m, &d);
sig.connect(&s::sm);
sig.connect(o());
sig.connect(lambda);
sig.connect(gen_lambda);
// emit a signal
sig();
}The slot invocation order when emitting a signal is unspecified, please do not rely on it being always the same.
That first example was simple but not so useful, let us move on to a signal that emits values instead. A signal can emit any number of arguments, below.
#include <sigslot/signal.hpp>
#include <iostream>
#include <string>
struct foo {
// Notice how we accept a double as first argument here.
// This is fine because float is convertible to double.
// 's' is a reference and can thus be modified.
void bar(double d, int i, bool b, std::string &s) {
s = b ? std::to_string(i) : std::to_string(d);
}
};
// Function objects can cope with default arguments and overloading.
// It does not work with static and member functions.
struct obj {
void operator()(float, int, bool, std::string &, int = 0) {
std::cout << "I was here\n";
}
void operator()() {}
};
int main() {
// declare a signal with float, int, bool and string& arguments
sigslot::signal<float, int, bool, std::string&> sig;
// a generic lambda that prints its arguments to stdout
auto printer = [] (auto a, auto && ...args) {
std::cout << a;
(void)std::initializer_list<int>{
((void)(std::cout << " " << args), 1)...
};
std::cout << "\n";
};
// connect the slots
foo ff;
sig.connect(printer);
sig.connect(&foo::bar, &ff);
sig.connect(obj());
float f = 1.f;
short i = 2; // convertible to int
std::string s = "0";
// emit a signal
sig(f, i, false, s);
sig(f, i, true, s);
}As shown, slots arguments types don't need to be strictly identical to the signal template parameters, being convertible-from is fine. Generic arguments are fine too, as shown with the printer generic lambda (which could have been written as a function template too).
Right now there are two limitations that I can think of with respect to callable handling: default arguments and function overloading. Both are working correctly in the case of function objects but will fail to compile with static and member functions, for different but related reasons.
Consider the following piece of code:
struct foo {
void bar(double d);
void bar();
};What should &foo::bar refer to? As per overloading, this pointer over member function does not map to a unique symbol, so the compiler won't be able to pick the right symbol. One way of resolving the right symbol is to explicitly cast the function pointer to the right function type. Here is an example that does just that using a little helper tool for a lighter syntax (In fact I will probably add this to the library soon).
#include <sigslot/signal.hpp>
template <typename... Args, typename C>
constexpr auto overload(void (C::*ptr)(Args...)) {
return ptr;
}
template <typename... Args>
constexpr auto overload(void (*ptr)(Args...)) {
return ptr;
}
struct obj {
void operator()(int) const {}
void operator()() {}
};
struct foo {
void bar(int) {}
void bar() {}
static void baz(int) {}
static void baz() {}
};
void moo(int) {}
void moo() {}
int main() {
sigslot::signal<int> sig;
// connect the slots, casting to the right overload if necessary
foo ff;
sig.connect(overload<int>(&foo::bar), &ff);
sig.connect(overload<int>(&foo::baz));
sig.connect(overload<int>(&moo));
sig.connect(obj());
sig(0);
return 0;
}Default arguments are not part of the function type signature, and can be redefined, so they are really difficult to deal with. When connecting a slot to a signal, the library determines if the supplied callable can be invoked with the signal argument types, but at this point the existence of default function arguments is unknown so there might be a mismatch in the number of arguments.
A simple work around for this use case would is to create a bind adapter, in fact we can even make it quite generic like so:
#include <sigslot/signal.hpp>
#define ADAPT(func) \
[=](auto && ...a) { (func)(std::forward<decltype(a)>(a)...); }
void foo(int &i, int b = 1) {
i += b;
}
int main() {
int i = 0;
// fine, all the arguments are handled
sigslot::signal<int&, int> sig1;
sig1.connect(foo);
sig1(i, 2);
// must wrap in an adapter
i = 0;
sigslot::signal<int&> sig2;
sig2.connect(ADAPT(foo));
sig2(i);
return 0;
}What was not made apparent until now is that signal::connect() actually returns a sigslot::connection object that may be used to manage the behaviour and lifetime of a signal-slot connection. sigslot::connection is a lightweight object (basically a std::weak_ptr) that allows interaction with an ongoing signal-slot connection and exposes the following features:
- Status querying, that is testing whether a connection is valid, ongoing or facing destruction,
- Connection (un)blocking, which allows to temporarily disable the invocation of a slot when a signal is emitted,
- Disconnection of a slot, the destruction of a connection previously created via
signal::connect().
A sigslot::connection does not tie a connection to a scope: this is not a RAII object, which explains why it can be copied. It can be however implicitly converted into a sigslot::scoped_connection which destroys the connection when going out of scope.
Here is an example illustrating some of the features:
#include <sigslot/signal.hpp>
#include <string>
int i = 0;
void f() { i += 1; }
int main() {
sigslot::signal<> sig;
// keep a sigslot::connection object
auto c1 = sig.connect(f);
// disconnection
sig(); // i == 1
c1.disconnect();
sig(); // i == 1
// scope based disconnection
{
sigslot::scoped_connection sc = sig.connect(f);
sig(); // i == 2
}
sig(); // i == 2;
// connection blocking
auto c2 = sig.connect(f);
sig(); // i == 3
c2.block();
sig(); // i == 3
c2.unblock();
sig(); // i == 4
}Moreover, Sigslot supports an extended slot signature with an additional sigslot::connection reference as first argument, which permits connection management from inside the slot. This extended signature is accessible using the connect_extended() method.
#include <sigslot/signal.hpp>
int main() {
int i = 0;
sigslot::signal<> sig;
// extended connection
auto f = [](auto &con) {
i += 1; // do work
con.disconnect(); // then disconnects
};
sig.connect_extended(f);
sig(); // i == 1
sig(); // i == 1 because f was disconnected
}The user must make sure that the lifetime of a slot exceeds the one of a signal, which may get tedious in complex software. To simplify this task, Sigslot can automatically disconnect slot object whose lifetime it is able to track. In order to do that, the slot must be convertible to a weak pointer of some form.
std::shared_ptr and std::weak_ptr are supported out of the box, and adapters are provided to support boost::shared_ptr, boost::weak_ptr and Qt QSharedPointer, QWeakPointer and any class deriving from QObject.
Other trackable objects can be added by declaring a to_weak() adapter function.
#include <sigslot/signal.hpp>
#include <sigslot/adapter/qt.hpp>
int sum = 0;
struct s {
void f(int i) { sum += i; }
};
class MyObject : public QObject {
Q_OBJECT
public:
void add(int i) const { sum += i; }
};
int main() {
sum = 0;
signal<int> sig;
// track lifetime of object and also connect to a member function
auto p = std::make_shared<s>();
sig.connect(&s::f, p);
sig(1); // sum == 1
p.reset();
sig(1); // sum == 1
// track an unrelated object lifetime
struct dummy;
auto l = [&](int i) { sum += i; };
auto d = std::make_shared<dummy>();
sig.connect(l, d);
sig(1); // sum == 2
d.reset();
sig(1); // sum == 2
// track a QObject
{
MyObject o;
sig.connect(&MyObject::add, &o);
sig(1); // sum == 3
}
sig(1); // sum == 3
}Thread safety is unit-tested. In particular, cross-signal emission and recursive emission run fine in a multiple threads scenario.
sigslot::signal is a typedef to the more general sigslot::signal_base template class, whose first template argument must be a Lockable type. This type will dictate the locking policy of the class.
Sigslot offers 2 typedefs,
sigslot::signalusable from multiple threads and uses std::mutex as a lockable. In particular, connection, disconnection, emission and slot execution are thread safe. It is also safe with recursive signal emission.sigslot::signal_stis a non thread-safe alternative, it trades safety for slightly faster operation.