Nothing here is specific to Rust and applies to any terminal app in any language that spawns a child process.
Nothing, that is, except for the examples, the source code, the libraries, and the linked references. But nothing else.
Fixing Ctrl+C in Rust terminal apps: Child process management
11–20 of 62 posts
Re: Fixing Ctrl+C in Rust terminal apps: Child process management
#12Fearless concurrency with Rust unless you are worried about lifecycle management, threads/co-operation and general ergonomics. Even modern c++ might be better at this (gasp!) with std::jthread
Re: Fixing Ctrl+C in Rust terminal apps: Child process management
#13Fearless concurrency with Rust unless you are worried about lifecycle management, threads/co-operation and general ergonomics. Even modern c++ might be better at this (gasp!) with std::jthread
Heretic!
Re: Fixing Ctrl+C in Rust terminal apps: Child process management
#14This title was close to being a garden path sentence, but ultimately avoided it.
Yes, daemonized children must always be killed; preferably by the parent, but any reaper would also work.
Re: Fixing Ctrl+C in Rust terminal apps: Child process management
#15Re: Fixing Ctrl+C in Rust terminal apps: Child process management
#16Fearless concurrency with Rust unless you are worried about lifecycle management, threads/co-operation and general ergonomics. Even modern c++ might be better at this (gasp!) with std::jthread
I believe Rust's std::thread::scope is an equivalent.
> Unlike non-scoped threads, scoped threads can borrow non-'static data, as the scope guarantees all threads will be joined at the end of the scope.
> All threads spawned within the scope that haven’t been manually joined will be automatically joined before this function returns.
Re: Fixing Ctrl+C in Rust terminal apps: Child process management
#17Nothing here is specific to Rust and applies to any terminal app in any language that spawns a child process.
Nothing, that is, except for the examples, the source code, the libraries, and the linked references. But nothing else.
Are you suggesting that the examples, source, libraries, and references for Rust make these mistakes, but other languages don't?
Re: Fixing Ctrl+C in Rust terminal apps: Child process management
#18Fearless concurrency with Rust unless you are worried about lifecycle management, threads/co-operation and general ergonomics. Even modern c++ might be better at this (gasp!) with std::jthread
Are there any languages that provide for or care about lifecycle management across address space boundaries? After fork() you're usually fucked and need explicit controls.
Re: Fixing Ctrl+C in Rust terminal apps: Child process management
#19Fearless concurrency with Rust unless you are worried about lifecycle management, threads/co-operation and general ergonomics. Even modern c++ might be better at this (gasp!) with std::jthread
Yes, and if you update to a version of LLVM that was released literally a week ago, jthread exists.
Re: Fixing Ctrl+C in Rust terminal apps: Child process management
#20[deleted]