Commit ff6e8371 authored by Marian Triebe's avatar Marian Triebe

Fix some typos

parent b9f000ae
......@@ -14,7 +14,7 @@
namespace caf::detail {
/// Enables destroying, construcing and serializing objects through type-erased
/// Enables destroying, constructing and serializing objects through type-erased
/// pointers.
struct meta_object {
/// Stores a human-readable representation of the type's name.
......
......@@ -24,7 +24,7 @@
namespace caf::detail {
/// Replacement for `std::pmr::monotonic_buffer_resource`, which sadly is not
/// available on all platforms CAF currenlty supports. This resource does not
/// available on all platforms CAF currently supports. This resource does not
/// support upstream resources and instead always uses `malloc` and `free`.
class CAF_CORE_EXPORT monotonic_buffer_resource {
public:
......
......@@ -176,7 +176,7 @@ public:
}
private:
// -- member vairables -------------------------------------------------------
// -- member variables -------------------------------------------------------
counting_pointer ptr_;
};
......
......@@ -12,7 +12,7 @@ namespace {
using int_fun = caf::detail::unique_function<int()>;
int fourty_two() {
int forty_two() {
return 42;
}
......@@ -61,7 +61,7 @@ CAF_TEST(default construction) {
}
CAF_TEST(raw function pointer construction) {
int_fun f{fourty_two};
int_fun f{forty_two};
CHECK_VALID(f);
}
......@@ -90,7 +90,7 @@ CAF_TEST(custom wrapper construction) {
}
CAF_TEST(function move construction) {
int_fun f{fourty_two};
int_fun f{forty_two};
int_fun g{std::move(f)};
CHECK_INVALID(f);
CHECK_VALID(g);
......@@ -122,15 +122,15 @@ CAF_TEST(custom wrapper move construction) {
CAF_TEST(function assign) {
size_t instances = 0;
int_fun f;
int_fun g{fourty_two};
int_fun g{forty_two};
int_fun h{new instance_counting_wrapper(&instances)};
CAF_CHECK(instances == 1);
CHECK_INVALID(f);
CHECK_VALID(g);
CHECK_VALID(h);
f = fourty_two;
g = fourty_two;
h = fourty_two;
f = forty_two;
g = forty_two;
h = forty_two;
CAF_CHECK(instances == 0);
CHECK_VALID(f);
CHECK_VALID(g);
......@@ -140,7 +140,7 @@ CAF_TEST(function assign) {
CAF_TEST(move assign) {
size_t instances = 0;
int_fun f;
int_fun g{fourty_two};
int_fun g{forty_two};
int_fun h{new instance_counting_wrapper(&instances)};
CAF_CHECK(instances == 1);
CHECK_INVALID(f);
......
......@@ -16,7 +16,7 @@ using int_dict = dictionary<int>;
} // namespace
CAF_TEST(construction and comparions) {
CAF_TEST(construction and comparison) {
int_dict xs;
CAF_CHECK_EQUAL(xs.empty(), true);
CAF_CHECK_EQUAL(xs.size(), 0u);
......
......@@ -20,7 +20,7 @@ using namespace std::string_literals;
using namespace caf;
// 20 integer wrappers for building a variant with 20 distint types
// 20 integer wrappers for building a variant with 20 distinct types
#define i_n(n) \
class i##n { \
public: \
......
......@@ -37,7 +37,7 @@ enum connection_state {
no_route_to_receiving_node,
};
/// Returns whether the connection state requries a shutdown of the socket
/// Returns whether the connection state requires a shutdown of the socket
/// connection.
constexpr bool requires_shutdown(connection_state x) noexcept {
// Any enum value other than await_header (0) and await_payload (1) signal the
......
......@@ -102,7 +102,7 @@ public:
instance(abstract_broker* parent, callee& lstnr);
/// Handles received data and returns a config for receiving the
/// next data or `none` if an error occured.
/// next data or `none` if an error occurred.
connection_state handle(execution_unit* ctx,
new_data_msg& dm, header& hdr, bool is_payload);
......
......@@ -124,7 +124,7 @@ struct fixture {
skip_client_side_ca ? &dummy : &client_side_config.openssl_cafile},
{"cert.2.pem", &client_side_config.openssl_certificate},
{"key.2.pem", &client_side_config.openssl_key}};
// return if any file is unreadable or non-existend
// return if any file is unreadable or non-existent
for (auto& x : cfg) {
auto path = cd + x.first;
if (access(path.c_str(), F_OK) == -1) {
......
......@@ -90,7 +90,7 @@ the inspection API.
We strongly recommend using the fixed-width integer types in all user-defined
messaging types. Consistently using these types over ``short``, ``int``,
``long``, etc. avoids bugs in heterogeneous environemnts that are hard to
``long``, etc. avoids bugs in heterogeneous environments that are hard to
debug.
.. _writing-inspect-overloads:
......
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