undefined | Better HN

0 pointslosvedir2y ago0 comments

Total rust newb here, but does that need the full async story, or is it a limitation of an API somewhere? From the point of view of the code using the request's response could you use a channel with recv_timeout? Is the problem there that the thread with the socket connection is still going and there's no way to stop it?

0 comments

insanitybit2y ago

The ability to cancel an operation without talking to the operating system requires that your program has yield points. That yielding is what allows another part of the program to take control and say "OK, I'm done with you now, no need to finish".

Yes, the problem is that your thread would continue to perform work even if you stopped waiting on it.

vc8f6vVV2y ago

Maybe I don't understand the complexity, but in good old Ruby I can easily stop a thread if I don't need result anymore. No async needed and no yield points necessary. Doesn't it apply to Rust too?

insanitybit2y ago

I assume that Ruby does in fact have yield points in some form, such as a global lock. Killing a thread is only possible (for a pthread) via the `pthread_cancel` API. That API is very dangerous and is generally not something you'd ever want to use manually - the thread will not clean up any memory or other resources, any shared memory is left in a tricky state.

To gracefully shut a thread down you need yielding of some kind.

j / k navigate · click thread line to collapse

0 pointslosvedir2y ago0 comments

0 comments

insanitybit2y ago

Yes, the problem is that your thread would continue to perform work even if you stopped waiting on it.

vc8f6vVV2y ago

Maybe I don't understand the complexity, but in good old Ruby I can easily stop a thread if I don't need result anymore. No async needed and no yield points necessary. Doesn't it apply to Rust too?

insanitybit2y ago

To gracefully shut a thread down you need yielding of some kind.

j / k navigate · click thread line to collapse