don't require tokio rt-multi-thread feature#290
Conversation
|
Hello @lunixbochs |
|
done |
|
How exactly does this work? Why is it necessary to spawn a new thread, create a tokio runtime on that thread, send the runtime back, and then exit the thread that created it? |
c0f7fa8 to
f2f4c93
Compare
|
Wow, I think I was completely on autopilot. I'd only done basic compile+println testing because existing versions of Accerciser still don't work with Accesskit on Linux due to #241 Sending a handle back and parking the thread on a sleep works much better. I tested this approach further by manually connecting to the bus and verifying some atspi methods work. |
|
This approach looks good to me. I just belatedly approved the CI workflow. |
|
The winit example seem to still work properly with the |
|
I just realized I can move the runtime into the thread on creation, which simplifies the code quite a bit. |
No description provided.