What needs to happen for WASM support?

[FelixBrakel]

I know the tokio runtime needs to support WASM which is only just starting to get implemented. Are there any other things that need to be addressed?

[Nerixyz]

Are you talking about browser WASM or WASI? Because tokio is currently stabilizing WASI.

[FelixBrakel]

Ah I didn't notice that they are stabilizing WASI, not WASM. I was looking to use this in a web app so WASM would be what I require for that.

[Nerixyz]

In my opinion this library is overkill for use in the browser. Its main advantage is joining and receiving messages from many channels efficiently. In a browser environment you usually only join one or in some cases two channels at one time. In the browser, you have to use the WebSocket(-Stream) API to connect to IRC, so there's not really any point in using tokio there since the browser will do most of the event scheduling for you.

I think one possible step could be to rip out the IRC parsing/writing part of this crate for use in other environments.