[FEATURE] - Add Support for WASM

[tqwewe]

Feature Description

Kameo currently hasn't been tested on in WASM targets. Having kameo actors work in the browser or on WASM targets would be a great feature to have.

Motivation

More platforms == better!

Proposed Solution

Tokio seems to have partial support for WASM as documented here: https://docs.rs/tokio/latest/tokio/#wasm-support

The only feature kameo has enabled on tokio which isn't listed as a supported WASM featue in tokio is tracing. However this can very easily be toggled depending on the build target.

[tqwewe]

I believe this can be closed thanks to #142, but if anyone has any issues please let me know

[Avi-D-coder]

Doesn't this linkme issue dtolnay/linkme#86 prevent wasm support?

[bmitc]

@tqwewe We are unable to build a Kameo network actor into a WASM application due to the linkme dependency not supporting WASM, as linked above.

This is a major blocker for us, and we may need to factor out Kameo network actors.

Do you have any suggestions as to a workaround for this? Is there a way to put the linkme dependency behind a feature flag. (I don't know what it's used for.)

[tqwewe]

@bmitc Unfortunately it seems like linkme isn't supported on wasm still: dtolnay/linkme#109

With the way kameo is implemented, and mainly in regards to how it doesn't use an enum for messages, and instead is done with traits, linkme is needed for remote actor messaging. If you don't need remote actors in your wasm project, then I believe it should compile. But for now it seems like wasm isn't supported with remote actor messaging due to linkme.