You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
Pull Request resolved: #441
looks like i failed to actually commit the change requested in https://www.internalfb.com/diff/D77744864?dst_version_fbid=708027588783326&transaction_fbid=697159643193767. this fixes it and also improves the typed references PortRef and OncePortRef introductions to mention that their message types require `RemoteMessage`.
Reviewed By: mariusae
Differential Revision: D77864737
fbshipit-source-id: 8d27858eb327c8753543636d5fb0ddfc6b05e509
> **Note**: While `ActorRef::attest` can be used to construct a reference from an `ActorId`, it should generally be avoided. Instead, prefer using the `ActorRef` returned from `ActorHandle::bind()`, which guarantees that the actor is actually running and bound to a mailbox. `attest` is unsafe in the sense that it bypasses that guarantee.
26
+
25
27
Unlike `ActorHandle<A>`, an `ActorRef` is just a reference — it doesn’t guarantee that the actor is currently running. It's primarily used for routing and type-safe messaging across `Proc`s.
26
28
27
29
### Definition
@@ -48,8 +50,9 @@ This allows the port to be sent across the network or passed into other messages
0 commit comments