Skip to content
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.

Sign up for GitHub

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

Jump to bottom

drop impl for Process shouldn't wait() #14410

Closed
glandium opened this issue May 25, 2014 · 2 comments
Closed

drop impl for Process shouldn't wait() #14410

glandium opened this issue May 25, 2014 · 2 comments

Comments

@glandium
Copy link
Contributor

My use-case is that i want to spawn a (detached) subprocess that survives the parent process. The equivalent of doing "command&" in a shell script.

Per IRC discussion:
forget() it when you're done with it?
it probably shouldn't wait in the destructor
should probably have a separate wait method
afaik we've been trying to avoid blocking destructors
glandium: it could be marked #[must_use] and only be destroyed with a wait or detach method, for example
@emberian
Copy link
Member

cc @alexcrichton

@alexcrichton
Copy link
Member

Closing as a dupe of #13854, but copying comments over to that one.

@alexcrichton alexcrichton mentioned this issue May 25, 2014
Closed
@glandium glandium mentioned this issue May 27, 2014
Closed
bors added a commit to rust-lang-ci/rust that referenced this issue Jun 5, 2023
@bors
Auto merge of rust-lang#14410 - Veykril:query-lru-capacities, r=Veykril
fc8c513 
internal: Add config to specifiy lru capacities for all queries

Might help figuring out what queries should be limited by LRU by default, as currently we only limit `parse`, `parse_macro_expansion` and `macro_expand`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alexcrichton @emberian @glandium