I do have a peculiar way of saying things sometimes. I didn’t mean to put myself down, but more so that I know I can make mistakes and am open to suggestions. Still, thank you!

My goal is to expand the object capability environment and make it easily usable in Rust. Here’s an implementation of the greeter actor using the API that I made:

// Vat Connector currently doesn't work, since vats are not implemented yet
let vat_connector = Some(VatConnector::new());
// New actormap inside vat
let am = make_actormap(vat_connector);

// Create a new constructor, greeter, that takes in the greeter's name to build an actor
constructor!(greeter, |_bcom: Rc<dyn Bcom>, my_name: String| {
    // Creates a behavior for the actor that takes in a String to say hello to
    behavior!(|your_name: String| -> String {
        // Value is returned to handle different responses, but I will clean this up to only return the String itself
        // Also, Value is for JSON. The API should use Syrup for OCapN
        Value::String(format!(
            "Hello {}, my name is {}",
            your_name, my_name
        ))
    })
});

// New actor greeter alice
let alice = actormap_direct_run!(&am, { spawn!(greeter, "Alice") });

// Alice greets Bob
assert_eq!(
    "Hello Bob, my name is Alice",
    actormap_direct_run!(&am, { call!(alice, "Bob") })?
);

This code works using the library. There are still many things I would like to clean up and change, as indicated by the comments. I just want to make it easier to create applications that interpret object capabilities. There are a lot of things that the library does different than Goblins (type restrictions, uses enums for return values, traits instead of meta types, etc.), but it mostly follows a similar philosophy of having a library that allows you to create an app that relies on object capability.