Add Socket.opened implementation

[Kakapio]

#441
I'm a bit confused regarding the actual implementation of Socket.opened itself. I created all the necessary bindings, same as the ones already implemented, but I'm not sure if I'm done. The Socket struct confuses me. I know the inner is the bound JS object itself, and the rest are mostly streams and options. What do Options such as close do? They are used in Tokio traits such as AsyncWrite. It looks like to me that particular one returns whether the Socket has closed yet, and the implementation also indicates that. I tried to decipher what I think is the original implementation of opened but have not been successful in understanding it. I added an opened Option to the Socket struct but am not sure of what to do with it.

Would it be incorrect to just implement it in AsyncRead.poll_read() ?

I think I just have to use reflection to grab the opened value on poll_read()?

[kflansburg]

#441 I'm a bit confused regarding the actual implementation of Socket.opened itself. I created all the necessary bindings, same as the ones already implemented, but I'm not sure if I'm done. The Socket struct confuses me. I know the inner is the bound JS object itself, and the rest are mostly streams and options. What do Options such as close do? They are used in Tokio traits such as AsyncWrite. It looks like to me that particular one returns whether the Socket has closed yet, and the implementation also indicates that. I tried to decipher what I think is the original implementation of opened but have not been successful in understanding it. I added an opened Option to the Socket struct but am not sure of what to do with it.

Would it be incorrect to just implement it in AsyncRead.poll_read() ?

I think I just have to use reflection to grab the opened value on poll_read()?

Have you seen https://developers.cloudflare.com/workers/runtime-apis/tcp-sockets/#socket?
This was the primary thing that I consulted when I wrote the original Rust wrappers.

[kflansburg]

Looks reasonable to me, we probably need to think about adding tests for this API.

Edit: To answer your question, I think we could do something clever with opened in the Stream implementation, but I don't think its necessary for now.