Dominik Charousset
Dominik Charousset
Flows currently only work locally and can transfer data through asynchronous buffers. The new streams should complement the async buffers with a way that also works in a distributed environment.
TODO item from https://github.com/actor-framework/actor-framework/pull/980. Adding a `type` tag to the thread hooks allows users to pin certain groups of threads to different cores. The these probably boil down to: 1....
It appears that `WSApoll` is buggy: http://daniel.haxx.se/blog/2012/10/10/wsapoll-is-broken/
The function `put_missing` is supposed to provide a high-level insertion function for `settings`. However, it currently only works with builtin types.
We don't have an official versioning policy yet, but we generally follow the policy that patch-level changes shall be backwards compatible. Hence, applications that expect CAF version 0.18.1 should be...
The meta objects live in the `detail` namespace and are thus private to CAF. Currently, there are only two public function for interacting with the meta objects table: ```cpp string_view...
Currently, actor handles have no type information. To be clear, we cannot provide this information for all actor types. For proxies, we simply do not have the type information at...
The latest additions to customize `config_value` via `config_value_access`, don't play nicely with the current handling of consumers. For example, passing a `double` to a field that expects an `int` (or...
There is a potential (yet very unlikely) deadlock in the CAF logger: after receiving an empty message as part of shutting down the actor system, the logger thread stops reading...
Original discussion see [stackoverflow](https://stackoverflow.com/questions/45589227/customizing-c-caf-framework).