summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorkyren <kerriganw@gmail.com>2018-02-19 18:16:43 -0500
committerkyren <kerriganw@gmail.com>2018-02-19 18:16:43 -0500
commit8824a236b2b156f107e2bd0c0d49220b570ae517 (patch)
tree5ce8957fce64df5c0ca85936f9deb2cc5ac34792 /README.md
parenta49ea51b79ff129f807b17b1510086377dac557f (diff)
downloadmlua-8824a236b2b156f107e2bd0c0d49220b570ae517.zip
Remove slightly triggering, and now misleading, language from README
Diffstat (limited to 'README.md')
-rw-r--r--README.md13
1 files changed, 3 insertions, 10 deletions
diff --git a/README.md b/README.md
index cc7242d..02e9b4c 100644
--- a/README.md
+++ b/README.md
@@ -115,13 +115,6 @@ If you encounter them, a bug report would be very welcome:
*absolutely* a bug, particularly because without `LUA_USE_APICHECK` it would
generally be unsafe.
* Lua C API errors are handled by lonjmp. *ALL* instances where the Lua C API
- would longjmp should be protected from Rust, except in a few cases of
- internal callbacks where there are only Copy types on the stack. If you
- detect that `rlua` is triggering a longjmp over Rust stack frames (other
- than the internal ones where this is intentional), this is a bug! (NOTE: I
- believe it is still an open question whether technically Rust allows longjmp
- over Rust stack frames *at all*, even if there are only Copy types on the
- stack. Currently `rlua` uses this to avoid having to write a lot of messy C
- shims. It *currently* works fine, and it is difficult to imagine how it
- would ever NOT work, but what is and isn't UB in unsafe Rust is not
- precisely specified.)
+ 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!