Neverlord on neverlord
Get rid of detail::shared_spinl… Re-implement work-stealing queu… Fix performance bottleneck: vec… and 1 more (compare)
request()..await()and then set the behavior later by calling
init_global_meta_objectsif you write a custom
main, cf. https://github.com/actor-framework/actor-framework/blob/master/libcaf_core/caf/init_global_meta_objects.hpp#L61).
a.home_system().node() != b.home_system().node(), but then realized these both return the same
node_id. I then tried
a.node() != b.node(), which works as expected. Is this a bug, or am I just misunderstanding? I am still on CAF 0.17.6.
This might help: https://www.cafcademy.com/articles/monitoring-and-linking
If "nothing happens": are you just doing regular shutdown? Links only tear down other actors in case of an error.
message_passingshould help you getting started: https://github.com/actor-framework/actor-framework/tree/master/examples/message_passing