actor-model

ActorAdapter will ignore null message with "Adapter function returned null which is not valid as an .."

However, this seems not be documented. For instance, scaladoc/javadoc of pipeToSelf could mention it as well as any other place where adapters are used.

As can be seen in the docs currently, the Debug impl on Addr requires the actor to also implement Debug. This is not actually needed as its not used.

impl<A: Debug + Actor> Debug for Addr<A>

Implementing this manually as

impl<A> Debug for Addr<A>

would fix that.

This also applies to `

This function body causes an assertion error in the compiler (version 0.42.0 in this case but I also see it in a slightly modified version of 0.45.0). I couldn't find another issue for this yet but it's not easy to search for.

Found this on a hunch/check while looking at the error-flag code, hoping to fix with possible other changes

     let x: String = (error)

This results in:

Currently, WebSocket is working for client/server side. However, the browsers do not allow to create tcp connections direclty (which is the current implementation based). Instead, the web-sys must be used.

• Use a different WebSocket implementation if the target is wasm.
• wasm example of a client.

We would like to make it easier to write manifest files so that we aren't constantly filling the file with the cumbersome actor public keys. Instead, we would like to be able to use the string that is associated with the actor's call alias (which can be set and displayed using the wash command line).

Of course, the trick is in figuring out where to go get the actor from once you have its ca

Scala 2.11 was removed in zio/zio-actors#89

Lets add it back now thar ZIO-NIO supports 2.11