From 51339410c19311b42fc7d4f6f91a7fab22a01504 Mon Sep 17 00:00:00 2001 From: BatmanAoD Date: Tue, 16 Jul 2019 08:55:21 -0600 Subject: [PATCH] Update text/XXX-unwind-FFI.md Fix typo caught in review Co-Authored-By: bjorn3 --- text/XXX-unwind-FFI.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/XXX-unwind-FFI.md b/text/XXX-unwind-FFI.md index 9a280f64..27e7c2b1 100644 --- a/text/XXX-unwind-FFI.md +++ b/text/XXX-unwind-FFI.md @@ -82,7 +82,7 @@ unwinding across the FFI boundary is well-defined and safe, and in fact it can be a useful way to handle errors when working with certain C libraries, such as `libjpeg`. -Thus, the `may_panic` function may be makred `#[unwind(allow)]`, +Thus, the `may_panic` function may be marked `#[unwind(allow)]`, which ensures that the unwinding operation will be propagated to the caller rather than aborting the process. This annotation will also prevent the compiler