summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkyren <kerriganw@gmail.com>2018-03-06 07:04:50 -0500
committerkyren <kerriganw@gmail.com>2018-03-06 07:04:50 -0500
commit6a0264169a87c3d9634b4aa4d087c31c0fd4fcd3 (patch)
treea5a42e10f47d25075ffa896e490374ebcf78a714
parent6ab7f99315f1ec7055eade9e950b448d11a646cc (diff)
downloadmlua-6a0264169a87c3d9634b4aa4d087c31c0fd4fcd3.zip
README updates
-rw-r--r--README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index 02e9b4c..6b40dfe 100644
--- a/README.md
+++ b/README.md
@@ -84,6 +84,10 @@ There are some caveats to the panic / abort guarantee, however:
disabled and know that these cannot error. Eventually, `rlua` will support
memory limits on scripts, and those memory limits will cause regular memory
errors rather than OOM aborts.
+ * `rustc` version `1.24.0` on Windows contains a
+ [bug](https://github.com/rust-lang/rust/issues/48251) which affects `rlua`
+ error handling, turning any Lua script error into an abort. If you are
+ using Rust `1.24.0` on windows, please upgrade to `1.24.1`.
Yet another goal of the library is to, in all cases, safely handle panics
generated by Rust callbacks. Panic unwinds in Rust callbacks should currently
@@ -118,3 +122,5 @@ If you encounter them, a bug report would be very welcome:
would longjmp should be protected from Rust, except in internal callbacks
where this is intentional. If you detect that `rlua` is triggering a
longjmp over your Rust stack frames, this is a bug!
+ * If you can somehow handle a panic in a Rust callback from Lua, this is a
+ bug.