Send/Sync and async in Workers
I've been trying to use async with workers and it's becoming an ever greater problem 
. I wanted to see if anyone has thoughts on how to solve this problem other than forever trying to play wackamole and use workarounds.
Relatively simple example: I'd like to be able to define async blocks in a bigger function to do a few things in 'parallel', the 'easiest' way to do this is with something like BoxFuture where I pin the individual async blocks and put them in a
-
-
I wanted to have some discussion on this topic because I think it's a serious issue with workers-rs currently and I don't think wackamole is the right solution here, I wanted to potentially suggest that the crate instead consider pretending it does run in an async environment when it interacts with other types (use arc instead of rc, Rwlock instead of RefCell, etc) and tank the (let's be honest) negligible performance hit.
I think this is especially problematic with workers where you are likely to be doing a lot of async operations and being able to easily split up chains of work is going to have a real performance impact, so the crate should be looking to make this as ergonomic as possible.
. I wanted to see if anyone has thoughts on how to solve this problem other than forever trying to play wackamole and use workarounds.Relatively simple example: I'd like to be able to define async blocks in a bigger function to do a few things in 'parallel', the 'easiest' way to do this is with something like BoxFuture where I pin the individual async blocks and put them in a
FuturesUnordered<BoxFuture<'_, Result<()>>>-
Bucket-
Rc<RefCell<wasm_bindgen_futures::Inner>>I wanted to have some discussion on this topic because I think it's a serious issue with workers-rs currently and I don't think wackamole is the right solution here, I wanted to potentially suggest that the crate instead consider pretending it does run in an async environment when it interacts with other types (use arc instead of rc, Rwlock instead of RefCell, etc) and tank the (let's be honest) negligible performance hit.
I think this is especially problematic with workers where you are likely to be doing a lot of async operations and being able to easily split up chains of work is going to have a real performance impact, so the crate should be looking to make this as ergonomic as possible.
