projects
/
web.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
b721e48
)
add forum link
author
Ralf Jung
<post@ralfj.de>
Mon, 25 Nov 2019 11:29:35 +0000
(12:29 +0100)
committer
Ralf Jung
<post@ralfj.de>
Mon, 25 Nov 2019 11:29:35 +0000
(12:29 +0100)
ralf/_posts/2019-11-25-how-to-panic-in-rust.md
patch
|
blob
|
history
diff --git
a/ralf/_posts/2019-11-25-how-to-panic-in-rust.md
b/ralf/_posts/2019-11-25-how-to-panic-in-rust.md
index 83216ad909561630ab225bf0ec70f3e797ecec73..2c03da8e783d84fff83201eebafb5bafe8216259 100644
(file)
--- a/
ralf/_posts/2019-11-25-how-to-panic-in-rust.md
+++ b/
ralf/_posts/2019-11-25-how-to-panic-in-rust.md
@@
-1,9
+1,10
@@
---
title: "How to Panic in Rust"
categories: rust
---
title: "How to Panic in Rust"
categories: rust
+forum: https://internals.rust-lang.org/t/how-to-panic-in-rust/11368
---
---
-What exactly happens when you
write
`panic!()`?
+What exactly happens when you `panic!()`?
I recently spent a lot of time looking at the parts of the standard library concerned with this, and it turns out the answer is quite complicated!
I have not been able to find docs explaining the high-level picture of panicking in Rust, so this feels worth writing down.
I recently spent a lot of time looking at the parts of the standard library concerned with this, and it turns out the answer is quite complicated!
I have not been able to find docs explaining the high-level picture of panicking in Rust, so this feels worth writing down.