korken89[m]: > <@korken89:matrix.org> To my other `async` aficionados, does anyone know of a way to not poison the future generated from async to become `!Send`  when a `RefCell` is used across an `.await` point? I don't think it's possible to get around, but better to check. This as the `RefCell` needs to be stored in the anonymous "enum" type that encodes the state, and then that type would be poisoned by the `RefCell` to also be `!Send`.
> 
> What I'm trying to do is to share a thing between 2 arms of a `select` statement, and the `NoopMutex` internally uses a `RefCell`.

refcell isn't send, but in embassy at least futures don't have to be Send. that's a tokio-ism because it is work stealing