Skip to content

More robust treatment of uncaught panics for child threads #946

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

Open
aturon opened this issue Mar 5, 2015 · 2 comments
Open

More robust treatment of uncaught panics for child threads #946

aturon opened this issue Mar 5, 2015 · 2 comments
Labels
breaking-change The RFC proposes a breaking change. T-lang Relevant to the language team, which will review and decide on the RFC. T-libs-api Relevant to the library API team, which will review and decide on the RFC.

Comments

@aturon
Copy link
Member

aturon commented Mar 5, 2015

Currently, an uncaught panic on a child thread will result in output to that thread's panic output handle (which is currently overridable).

This may not be a desirable default, and we probably want the behavior to be more thoroughly customizable.

See this previous RFC for some discussion on the topic.

@aturon aturon added A-wishlist breaking-change The RFC proposes a breaking change. labels Mar 5, 2015
@aturon
Copy link
Member Author

aturon commented Mar 5, 2015

Note: a change to the default would likely be a breaking change.

@blaenk
Copy link
Contributor

blaenk commented Mar 5, 2015

Yup.

@petrochenkov petrochenkov added T-lang Relevant to the language team, which will review and decide on the RFC. T-libs-api Relevant to the library API team, which will review and decide on the RFC. labels Jan 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change The RFC proposes a breaking change. T-lang Relevant to the language team, which will review and decide on the RFC. T-libs-api Relevant to the library API team, which will review and decide on the RFC.
Projects
None yet
Development

No branches or pull requests

3 participants