Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upFinalze behavior for uncaught panics in child threads #23078
Comments
aturon
added
the
A-threads
label
Mar 5, 2015
This comment has been minimized.
This comment has been minimized.
|
triage: P-backcompat-lang (1.0 beta) |
rust-highfive
added
the
P-backcompat-lang
label
Mar 5, 2015
rust-highfive
added this to the 1.0 beta milestone
Mar 5, 2015
aturon
added
the
I-needs-decision
label
Mar 5, 2015
This comment has been minimized.
This comment has been minimized.
|
This is not going to change in time for beta. In any case, the current behavior can be a default going-forward (it is a default we can live with), and then we can backwards compatibly add the ability to customize the behavior. Reclassifying: not 1.0 beta, and not 1.0; P-high. |
pnkfelix
added
the
P-medium
label
Mar 26, 2015
pnkfelix
removed this from the 1.0 beta milestone
Mar 26, 2015
pnkfelix
removed
the
P-backcompat-lang
label
Mar 26, 2015
This comment has been minimized.
This comment has been minimized.
theemathas
commented
Apr 10, 2015
|
Related to #23172 |
huonw
added
I-nominated
T-libs
and removed
I-needs-decision
labels
Jan 8, 2016
This comment has been minimized.
This comment has been minimized.
|
With a stable release, the introduction of panic handlers, and the introduction of panic propagation, I'm going to close this issue now. |
alexcrichton
closed this
Jan 21, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
aturon commentedMar 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, and the corresponding RFC issue.
We need to make a decision here before 1.0.