Implement non-null guarantee for handles
CAF now assumes handle types (actor_addr, actor, typed_actor<...>) to be non-null. Actors can break this assumption by constructing handles with `unsafe_actor_handle_init`, but any attempt to use such a handle causes undefined behavior. This gives handles reference-like semantics, as opposed to pointer-like semantics. Relates #461.
Showing
Please register or sign in to comment