Commit 227ba3ed authored by Matthias Vallentin's avatar Matthias Vallentin

Directly include log level definitions

We encountered a build issue when the log level defitions haven't been
included directly. Perhaps it's a subtle transitive include issue.
Regardless, it's always prudent to include all headers directly where
they are used.
parent 3f135a62
......@@ -32,6 +32,7 @@
#include "caf/deep_to_string.hpp"
#include "caf/detail/arg_wrapper.hpp"
#include "caf/detail/pretty_type_name.hpp"
#include "caf/detail/log_level.hpp"
#include "caf/detail/ringbuffer.hpp"
#include "caf/detail/scope_guard.hpp"
#include "caf/detail/shared_spinlock.hpp"
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment