-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reimplement Core::run #143
Comments
This is included as part of #141. 🍾 |
That PR has landed. You can now use |
Thanks. I'm using |
Could you describe a bit more what specifically you are trying to achieve?
…On Sat, Feb 24, 2018 at 3:57 PM Alan Somers ***@***.***> wrote:
Thanks. I'm using CurrentThread::block_on_all and it's working. I'm
relying on the ability to call Handle::current outside of the Reactor
loop, though, and I'm not sure that's guaranteed to work.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#143 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAAYJJzhHv4MoV9iVzEDcQaaFR5vjXJcks5tYKHzgaJpZM4SKBTe>
.
|
See #153 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tokio-core
'sCore::run
method evaluated a future to completion, then returned the result.tokio
currently lacks any equivalent.current_thread::spawn
is the closest, but it can't return a result. Please consider adding an equivalent method totokio
.The text was updated successfully, but these errors were encountered: