ac21874d11
(cargo-release) start next development iteration 0.14.3-alpha.0
2018-08-06 19:09:27 -04:00
ca8326475f
(cargo-release) version 0.14.2
2018-08-06 19:09:09 -04:00
e4de847395
(cargo-release) start next development iteration 0.14.2-alpha.0
2018-08-05 12:35:05 -04:00
e6ca00b65c
(cargo-release) version 0.14.1
2018-08-05 12:33:26 -04:00
8366960368
Update to failure 0.1.2, rename deprecated methods
2018-08-05 11:48:25 -04:00
e6688e1db2
very small doc fixes
2018-08-05 09:51:32 -04:00
2d4f4b95c8
(cargo-release) start next development iteration 0.14.1-alpha.0
2018-06-29 01:28:28 -04:00
0cab2e25de
(cargo-release) version 0.14.0
2018-06-29 01:25:15 -04:00
02bc8da203
Prepare for 0.14.0 release
2018-06-29 01:24:28 -04:00
60bfe1fb07
Nope, require failure 1.0 because otherwise it depends on backtrace automatically
2018-03-20 16:23:23 -04:00
a22c23ae26
rely on failure 0.1.2 from git to get backtrace disabled by default
...
without relying on an unreleased 1.0 API. Trying to get rid of the special
chucklefish hack branches in the meantime before 1.0.
2018-03-20 15:17:27 -04:00
5aa22de68e
Use git dependency on failure 1.0 for right now
2018-03-20 14:07:32 -04:00
f0775f4a1a
Move several asserts to only be active with debug, bump alpha version number
2018-03-12 16:14:52 -04:00
964666e11b
Use criterion for benchmarking, add some simple benchmarks
2018-03-10 10:31:57 -05:00
6ab7f99315
Revert "Temporary fix for #71 . Remove when rust #48251 is fixed in stable."
...
This reverts commit 5d96ddc52a
2018-03-06 07:03:58 -05:00
0e9a70e688
(cargo-release) start next development iteration 0.13.1-alpha.0
2018-02-28 14:51:50 -05:00
e98d4d1827
Update changelog / cargo.toml in prep for 0.13
2018-02-28 14:44:16 -05:00
5d96ddc52a
Temporary fix for #71 . Remove when rust #48251 is fixed in stable.
2018-02-28 14:43:15 -05:00
a49ea51b79
Remove terrible awful no-good evil hack
...
The breakage is being addressed in rust itself.
2018-02-19 18:09:04 -05:00
e19a5b6481
Cleanup max upvalues constant a bit, add some luaconf.h assumptions
2018-02-19 18:03:18 -05:00
52eedfd378
I'm not going to release this as is, but I need to weigh my options
2018-02-16 23:43:30 -05:00
dec360f78f
Can.. can I do this? Is this a thing that actually works?
...
Drastic times and all that.
2018-02-16 22:01:41 -05:00
f0186d1799
Provisional "fix" for #71 . Requires nightly :(
2018-02-15 21:39:35 -05:00
6b46e8abe9
prepare for 0.12.2
2018-02-14 00:56:20 -05:00
c22aae461b
Some changes for panic correctness, stack usage correctness, and speed
2018-02-12 13:54:31 -05:00
9388a72d61
Update Cargo.toml for 0.12.1
2018-02-11 17:55:40 -05:00
61236e685f
Change changelog, readme, examples, Cargo.toml for 0.12 release
2018-02-10 19:04:18 -05:00
d4c80d44c8
Attempt to enable compiletest_rs on nightly on travis
2018-02-10 00:27:15 -05:00
f785a3abe4
Don't bother with a feature, just disable LUA_USE_APICHECK in release
2018-02-09 23:59:11 -05:00
84b009da03
A few small performance improvements
...
When 'debug_assertions' is not enabled, don't bother doing asserts in
stack_guard / stack_err_guard. Also, add an optional feature not enabled by
default to disable LUA_USE_APICHECK in release mode. Once the bugs in rlua that
allow you to trigger LUA_USE_APICHECK are fixed, this feature will be the
default behavior.
2018-02-09 01:22:34 -05:00
cbc882bad0
Bump cargo version to 0.11.0
2018-01-26 22:03:13 -05:00
0801104762
ACTUALLY expose RegistryKey API
...
Also fixes a safety issue with RegistryKey, where you could use RegistryKeys
with mismatching Lua instances.
2018-01-26 19:43:53 -05:00
79ba909db0
Experimentally use the failure crate for errors
2018-01-21 20:08:51 -05:00
443054f753
Update README, CHANGELOG, and Cargo.toml for 0.10.2
2017-12-17 01:14:11 -05:00
c67ae24c97
bump version for doc spelling fix
2017-12-05 00:16:35 -05:00
80a98ef29c
Couple of changes:
...
- 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 01:47:04 -05:00
cfa2b34a7b
Bump version to 0.9.7, update changelog
2017-11-08 14:07:48 -05:00
00a3153ae0
Bump version / changelog for 0.9.6
2017-10-26 16:53:14 -04:00
8592af1b16
Bump version to 0.9.5, update changelog
2017-10-25 14:55:05 -04:00
4bbeeb2b2d
Update to 0.9.4, update changelog
2017-10-24 08:59:55 -04:00
401c06cfe6
Bump cargo version to 0.9.3, update changelog.
2017-10-14 19:27:24 -04:00
ef538d8757
Update rlua to 0.9.2, add SOME kind of changelog.
2017-09-24 19:32:26 -04:00
ec088300f2
Specify gcc crate dependency with minimum bound on version with Build
2017-09-09 21:04:57 -04:00
1efef92570
I guess I need to bump the cargo version even to change the badge.
2017-08-02 17:43:44 -04:00
fffeb9701b
Badge has wrong url, I guess it doesn't expect the github portion
2017-08-02 17:42:58 -04:00
b42d613c5b
Update Cargo.toml for 0.9, add travis-ci badge
2017-08-02 17:37:29 -04:00
2553623b65
Provide custom allocators that ensure that OOM results in an abort
...
(closes unsafety hole)
2017-08-02 16:33:48 -04:00
3f20319a84
Use rustyline for the REPL
...
This makes the REPL more usable as you can now edit lines and recall
previously executed statements.
2017-08-02 14:32:45 +02:00
4549abbb85
Two major API changes to start with:
...
* Callbacks have generic argument and return types
* All variadics are done with tuples
2017-07-31 01:21:41 -04:00
eafe4c7c30
cargo version bump for linking fix
2017-07-09 17:20:51 -04:00
kyren