Steve Schoettler

this PR includes capability provider sources and replaces cap provider binaries. I didn't change any actors - they are stuck in an examples PR

@brooksmtownsend I did remove the claim and left a comment in the Makefile: https://github.com/wasmCloud/wasmcloud-otp/blob/eefc8877aaf1884d4495d86d8ab1efbce2236524/host_core/test/fixtures/actors/echo_unpriv/Makefile#L6 The test "fails" though, but Kevin said a failure is expected .. Is there a problem...

will do - thanks!

post mvp - we're not sure if this is a likely scenario

I started to implement support for this in the code generator, assuming a new host function `__host_send` with the same signature as `__host_call`. The expectation from the actor is that...

I thought of another way to implement async calls from actors that is a bit more generic, and wouldn't require generating all new interfaces. It would require putting the code...

One advantage of this versus the idea we had of modifying code-generated interfaces to add async send functions is that this works even without invoking a host_send message- it can...

The second idea above (exported async function) is similar to a special case of actor-invoking-actor, where the invoked actor is always "self", and the invocation isn't signed and always runs...

tossing another example into the mix .. [Smithy](https://awslabs.github.io/smithy/index.html) was designed to solve many of the same problems. AWS uses it to define interfaces for 250+ web services, and code generators...

This was in wash 0.10.0 on m1 mac with macos 12.3.1