Kevin Flansburg

Superseded by #450

This matches the behavior of the JavaScript API, which returns from `connect` immediately (it is not a `Promise`), and thus does not indicate whether the connection has been established with...

Does reading return an error? I think it _should_ error, but I will have to check the JavaScript behavior.

@dom96 thoughts on this behavior?

Yep, I think it would be reasonable to add that to the Rust API. Also looks like we need to add it to our JavaScript docs.

I'm not sure if this will be possible, there are a few APIs that we are wanting to change in place which prevents a purely additive feature. I did run...

Unfortunately, while `Env` is `Send`, `r2::Bucket` is not. I'm slowly making progress in #481 on improving this, but I'm wondering if there is a better approach then just making everything...

Ok, great, I’ll check that out. Would be nice to have a generic solution.

I think something slightly simpler might be possible, I added a generic macro, [`worker::send`](https://github.com/cloudflare/workers-rs/blob/fca35f4c290f949c4fbefd19aaa0652acd62d992/worker-macros/src/lib.rs#L28), which does: ```rust SendFuture(async move { #fn_body }).await ``` where `SendFuture` is marked as `Send` See...

@avsaase I think this might be a cleaner direction for us to go to fix the remaining `!Send` issues ^