Skip to content

Commit 91dd12b

Browse files
dbdrtesuji
authored andcommitted
Use simpler link syntax
Thanks @lzutao Co-authored-by: lzutao <[email protected]>
1 parent 76d0799 commit 91dd12b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/unwinding.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ panics can only be caught by the parent thread. This means catching a panic
3131
requires spinning up an entire OS thread! This unfortunately stands in conflict
3232
to Rust's philosophy of zero-cost abstractions.
3333

34-
There is an API called [`catch_unwind`][catch_unwind] that enables catching a panic
34+
There is an API called [`catch_unwind`] that enables catching a panic
3535
without spawning a thread. Still, we would encourage you to only do this
3636
sparingly. In particular, Rust's current unwinding implementation is heavily
3737
optimized for the "doesn't unwind" case. If a program doesn't unwind, there
@@ -48,4 +48,4 @@ point is up to you, but *something* must be done. If you fail to do this,
4848
at best, your application will crash and burn. At worst, your application *won't*
4949
crash and burn, and will proceed with completely clobbered state.
5050

51-
[catch_unwind]: https://doc.rust-lang.org/std/panic/fn.catch_unwind.html
51+
[`catch_unwind`]: https://doc.rust-lang.org/std/panic/fn.catch_unwind.html

0 commit comments

Comments
 (0)