| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2018-02-07 | Don't keep the unref list around forever after Lua is dropped | kyren | |
| 2018-02-06 | Lots of changes, not sure if actually safe yet. | kyren | |
| * Make Lua Send * Add Send bounds to (nearly) all instances where userdata and functions are passed to Lua * Add a "scope" method which takes a callback that accepts a `Scope`, and give `Scope` the ability to create functions and userdata that are !Send, *and also functions that are not even 'static!*. | |||
| 2018-02-06 | fix missing unwrap in tests | kyren | |
| 2018-02-06 | Don't panic on mismatched `RegistryKey` use, instead return error | kyren | |
| 2018-02-06 | Slightly different strategy with RegistryKey values | kyren | |
| Provide a method for automatic cleanup of expired RegistryKey values, so that manually cleaning up registry values is optional. | |||
| 2018-02-06 | test `owns_registry_value` | kyren | |
| 2018-02-06 | Add method to check whether a RegistryKey is owned by a given `Lua` instance | kyren | |
| 2018-02-06 | experimentally make `RegistryKey` Send | kyren | |
| 2018-02-05 | Set the metatable of __gc'ed userdata to something more informative | kyren | |
| 2018-01-27 | Use ptr::write to initialize uninitalized memory, NOT mem::replace | kyren | |
| 2018-01-27 | Simplify handling of userdata __gc and resurrected userdata. | kyren | |
| Now, simply remove the userdata table immediately before dropping the userdata. This does two things, it prevents __gc from double dropping the userdata, and after the first call to __gc, it prevents the userdata from being identified as any particular userdata type, so it cannot be misused after being finalized. This change thus removes the userdata invalidation error, and simplifies a lot of userdata handling code. It also fixes a panic bug. Because there is no predictable order for finalizers, it is possible to run a userdata finalizer that does not resurrect itself before a lua table finalizer that accesses that userdata, and this means that there were several asserts that were possible to trigger in normal Lua code in util.rs related to `WrappedError`. Now, finalized userdata is simply a userdata with no methods, so any use of finalized userdata becomes a normal script runtime error (though, with a potentially confusing error message). As a future improvement, we could set a metatable on finalized userdata that provides a better error message. | |||
| 2018-01-26 | Bump cargo version to 0.11.0 | kyren | |
| 2018-01-26 | update changelog for 0.11.0 | kyren | |
| 2018-01-26 | Update README for clarity, typofixes | kyren | |
| 2018-01-26 | Add an API that exposes the functionality of `lua_getuservalue` and ↵ | kyren | |
| `lua_setuservalue` | |||
| 2018-01-26 | ACTUALLY expose `RegistryKey` API | kyren | |
| Also fixes a safety issue with RegistryKey, where you could use RegistryKeys with mismatching Lua instances. | |||
| 2018-01-26 | Merge pull request #66 from jonas-schievink/docs | kyren | |
| Clarify a few docs | |||
| 2018-01-26 | __gc would be safe now, reword MetaMethod docs accordingly | Jonas Schievink | |
| 2018-01-26 | Additional `MetaMethod` docs | Jonas Schievink | |
| 2018-01-26 | create_function docs: mention what returning `Err` does | Jonas Schievink | |
| 2018-01-26 | Fix rustdoc rendering warning | Jonas Schievink | |
| 2018-01-26 | Don't use a `StdResult` alias for better docs. | Jonas Schievink | |
| This is a pretty opinionated change, but I find documentation to be clearer when using plain old names everybody understands immediately. | |||
| 2018-01-24 | Merge pull request #63 from chucklefish/failure | kyren | |
| Experimentally use the `failure` crate for errors | |||
| 2018-01-21 | Experimentally use the `failure` crate for errors | kyren | |
| 2017-12-17 | Missed unprotected call to luaL_ref | kyren | |
| 2017-12-17 | Update README, CHANGELOG, and Cargo.toml for 0.10.2 | kyren | |
| 2017-12-17 | Add automatic Lua "user accessible registry" keys | kyren | |
| Also, during the implementation of this, I noticed a problem with the 0.10 memory safety, which is that luaL_ref is also memory unsafe. I attempted to change the API to support luaL_ref potentially returning Result, but this change will cause an enormous amount of API chaos, (just as an example, it becomes impossible to implement Clone for LuaRef as is). Instead, luaL_ref now is guarded by gc_guard. | |||
| 2017-12-16 | Change API names, add unset function | kyren | |
| 2017-12-16 | auto formatting | kyren | |
| 2017-12-16 | API for registry access via string keys only (for now) | kyren | |
| Also includes some fixes for stack usage and changes an assert_eq to lua_assert | |||
| 2017-12-05 | spelling fix for my spelling fix | kyren | |
| 2017-12-05 | bump version for doc spelling fix | kyren | |
| 2017-12-05 | spelling fixes | kyren | |
| 2017-12-04 | extra space | kyren | |
| 2017-12-04 | Add `ExpiredUserData` error and avoid what was previously a panic | kyren | |
| Also make sure that panic messages clearly state that they are internal errors, so people report them as a bug. Since the only panics left are all internal errors, just move the internal error message into the panic / assert macros. | |||
| 2017-12-04 | Couple of changes: | kyren | |
| - Update readme, changelog, cargo version number in preparation for release - Remove panicking behavior on recursive callback calls, add additional error variant for recursive callback errors. | |||
| 2017-12-04 | more reorganization in an attempt to shrink the size of lua.rs | kyren | |
| 2017-12-04 | Move function and thread into their own modules, auto-formatting | kyren | |
| 2017-12-04 | Include garbage collector error type, remove unnecessary setmetatable wrapper | kyren | |
| 2017-12-04 | I *THINK* this might actually be it, is rlua 'm' safe now? | kyren | |
| 2017-12-03 | I believe this is all the external API changes necessary for 'm' safety | kyren | |
| 2017-12-03 | missing push_string calls in util | kyren | |
| 2017-12-03 | Couple of changes in preparation for 'm' safety: | kyren | |
| - auto formatting - add gc control to ffi - add gc_guard to util functions - use gc_guard to make util error handling functions never trigger __gc metamethod Lua errors even without __gc metatable wrapper - sort of a technicality, don't call luaL_requiref outside of the Lua constructor, as it could trigger the garbage collector when user code has had a chance to set __gc metamethods. Changes the API to load the debug table. | |||
| 2017-12-03 | more refactoring | kyren | |
| 2017-12-03 | remove specific protected functions in favor of generic protect_lua_call | kyren | |
| 2017-12-03 | missed stack size fix | kyren | |
| 2017-12-03 | More refactoring towards mem error safety | kyren | |
| 2017-12-03 | auto formatting | kyren | |
| 2017-12-03 | more refactoring trying to find a workable path to 'm' error safety | kyren | |
| 2017-12-02 | still making small structural changes | kyren | |
| slowly trying to refactor things until using all the protected calls in protected_ffi is workable | |||
 |
index : mlua | |
| High level Lua 5.4/5.3/5.2/5.1 (including LuaJIT) and Roblox Luau bindings to Rust with async/await support | cos |
| summaryrefslogtreecommitdiff |