29aa25a48b
Dont take wrapped panic in error_tostring()
2019-11-04 22:23:09 +00:00
85607d8bfc
Impl Drop for Lua
2019-10-17 17:05:42 +01:00
ec08a76a41
Don't store extra data in the lua_State extra space
2019-10-17 17:05:42 +01:00
c4fd7a9faf
Lua 5.1 support
2019-10-17 17:05:42 +01:00
676ffc0dfd
Rename LUA_LIB/LUA_INC variables and link static
2019-10-17 17:05:42 +01:00
430e2e07ea
Clear changelog and update license
2019-10-17 17:05:41 +01:00
b7c578c274
Replace libc with std::os::raw
2019-10-02 22:12:28 +01:00
224ed8ff52
Add mlua_derive proc macro module
2019-10-02 22:12:27 +01:00
cade76137a
Rerun build.rs if glue.c changed
2019-10-01 16:11:36 +01:00
cb109f6e36
Rename to mlua
2019-10-01 16:11:12 +01:00
9e06b10e50
Support defining custom lua include and lib pathes
2019-09-30 22:41:09 +01:00
2e5762f6e5
fmt glue.c
2019-09-30 22:34:47 +01:00
11e22d1cba
Temporary drop "compile-fail" tests due to unstable compiletest_rs crate
2019-09-30 22:34:20 +01:00
2ca4273ffb
Add call method to table
2019-09-30 22:15:27 +01:00
78480b5f31
Use main state to store extra data and auxiliary registries
2019-09-30 22:14:58 +01:00
54f4627195
Update tests (excl. compile-fail)
2019-09-29 13:03:32 +01:00
45159bfda7
Add Table::raw_remove method
2019-09-29 12:56:06 +01:00
0c230a3037
Allow to catch rust panics via pcall
2019-09-29 12:56:06 +01:00
b23ee6a162
cargo fmt
2019-09-29 12:56:03 +01:00
affa85feb0
Backport changes from rlua 0.16 (master branch)
2019-09-29 12:53:13 +01:00
53b352466e
Replace ffi module with implementation from "jcmoyer/rust-lua53" crate
2019-09-29 12:42:07 +01:00
14a68dd6d2
Add dyn to trait objects
2019-09-29 12:42:07 +01:00
47a8ac2b05
Allow only init Lua from an exiting state
2019-09-26 19:17:51 +01:00
b1aa8f8a80
Remove builtin lua
2019-08-08 18:54:08 +01:00
da3d4c4998
(cargo-release) version 0.15.3
2018-10-13 17:56:42 -04:00
d6998ca8fe
update changelog for 0.15.3
2018-10-13 17:54:42 -04:00
0c1e5c7c5d
fix broken .travis.yml
2018-10-13 17:51:44 -04:00
f02444e5a7
add rustfmt checks to travis (stable channel)
2018-10-13 17:48:16 -04:00
917b432aa5
Merge pull request #96 from sakridge/fix-num-traits-version
...
Update num-traits dependency to 0.2.6
2018-10-11 14:35:00 -04:00
da6e92d16d
Update num-traits dependency to 0.2.6
...
This crate requires i128 support which is not
added to num-traits until the 0.2.5 release and i128
detection is added in 0.2.6.
2018-10-11 10:40:03 -07:00
1a259284ab
(cargo-release) start next development iteration 0.15.3-alpha.0
2018-10-01 06:10:35 -04:00
8db6709fb8
(cargo-release) version 0.15.2
2018-10-01 06:10:18 -04:00
929036f2c8
Update changelog for one more 0.15 last minute addition
2018-10-01 06:09:54 -04:00
65d8ad2f86
Allow non-utf8 Lua source in load / exec / eval
2018-10-01 06:00:21 -04:00
8538874dd3
Whoops, misplaced assert
2018-10-01 05:31:28 -04:00
4625ac9d52
Some more minor guided tour updates
2018-10-01 05:24:11 -04:00
c7684fef32
Update comments in guided tour for recent additions
2018-10-01 05:20:05 -04:00
e49ecbd6be
(cargo-release) start next development iteration 0.15.2-alpha.0
2018-10-01 05:15:25 -04:00
5610748347
(cargo-release) version 0.15.1
2018-10-01 05:15:09 -04:00
51339ecb1d
Some documentation and changelog fixes
2018-10-01 05:14:43 -04:00
f8665ba334
(cargo-release) version 0.15.0
2018-10-01 04:53:22 -04:00
d8a43f79b0
Update changelog for 0.15, fix readme for earlier tuple size increase
2018-09-30 16:31:05 -04:00
167184ae76
Allow arbitrary [u8] Lua strings
2018-09-30 15:42:04 -04:00
8810c36979
Add test for i128 Lua round-trip
2018-09-26 21:13:25 -04:00
6d17a383df
Avoid mem::uninitialized in generic context as it is unsound with e.g. bool
2018-09-26 21:07:11 -04:00
58ce05ff9a
Improve the situation with numerical conversion
...
This is a somewhat involved change with two breaking API changes:
1) Lua::coerce_xxx methods now return Option (this is easier and faster than
dealing with Result)
2) rlua numeric conversions now allow more loss of precision
conversions (e.g. 1.5f32 to 1i32)
The logic for the first breaking change is that mostly the coerce methods are
probably used internally, and they make sense as low-level fallible casts and
are now used as such, and there's no reason to confuse things with a Result with
a large error type and force the user to match on the error which will hopefully
only be FromLuaConversionError anyway.
The logic for the second change is that it matches the behavior of
num_traits::cast, and is more consistent in that *some* loss of precision
conversions were previously allowed (e.g. f64 to f32).
The problem is that now, Lua::coerce_integer and Lua::unpack::<i64> have
different behavior when given, for example, the number 1.5. I still think this
is the best option, though, because the Lua::coerce_xxx methods represent how
Lua works internally and the standard C API cast functions that Lua provides,
and the ToLua / FromLua code represents the most common form of fallible Rust
numeric conversion.
I could revert this change and turn `Lua::eval::<i64>("1.5", None)` back into an
error, but it seems inconsistent to allow f64 -> f32 loss of precision but not
f64 -> i64 loss of precision.
2018-09-26 21:01:54 -04:00
c3d0110722
Return rlua::Error on out of range numeric conversions using num_traits::cast
2018-09-24 22:14:50 -04:00
6a5ec6b387
cargo fmt
2018-09-24 22:13:42 -04:00
70b67052c9
Upgrade rustyline to 2.0 to avoid confusion
2018-09-24 21:27:29 -04:00
14090821d3
Make the changes I proposed to PR #79
...
Allows people (maybe only I care about this?) to build rlua in weird
environments.
2018-09-16 21:18:24 -04:00
Alex Orlenko