sieve: ActorHandle will do (#423)

Summary:
Pull Request resolved: #423

all the actors in this program run on the same proc. accordingly, use `ActorHandle`s not `ActorRef`s.

Reviewed By: mariusae

Differential Revision: D77740531

fbshipit-source-id: 1e8f10d648e7d6bf63c224a054f6db83d417452c

Author: shayne-fletcher

hyperactor_mesh/examples/sieve.rs

@@ -17,7 +17,7 @@ use std::process::ExitCode;
 use anyhow::Result;
 use async_trait::async_trait;
 use hyperactor::Actor;
-use hyperactor::ActorRef;
+use hyperactor::ActorHandle;
 use hyperactor::Context;
 use hyperactor::Handler;
 use hyperactor::Named;
@@ -67,7 +67,7 @@ pub struct SieveActor {
     /// Prime used for filtering.
     prime: u64,
     /// Next actor in the sieve chain.
-    next: Option<ActorRef<SieveActor>>,
+    next: Option<ActorHandle<SieveActor>>,
 }
 
 #[async_trait]
@@ -76,13 +76,12 @@ impl Handler<NextNumber> for SieveActor {
         if msg.number % self.prime != 0 {
             match &self.next {
                 Some(next) => {
-                    next.send(this, msg)?;
+                    next.send(msg)?;
                 }
                 None => {
                     msg.prime_collector.send(this, msg.number)?;
-                    let child = SieveActor::spawn(this, SieveParams { prime: msg.number }).await?;
-                    let child_ref = child.bind();
-                    self.next = Some(child_ref);
+                    self.next =
+                        Some(SieveActor::spawn(this, SieveParams { prime: msg.number }).await?);
                 }
             }
         }