fa217d3706
Better Luau buffer type support.
...
- Add `Lua::create_buffer()` function
- Support serializing buffer type as a byte slice
- Support accessing copy of underlying bytes using `BString`
2024-03-28 13:05:01 +00:00
b62f2ee0f7
chore: make clippy happy ( #388 )
...
Co-authored-by: hzlinyiyu <hzlinyiyu@corp.netease.com >
2024-03-25 13:26:06 +00:00
83c075c72b
Implement IntoLua for RegistryKey
2024-02-29 22:45:32 +00:00
020e8a78a8
Impl FromLua for RegistryKey
2024-02-10 15:41:48 +00:00
3ca7b4942e
Implement IntoLua for &Value
2024-02-07 00:10:49 +00:00
1754226c74
Impl IntoLua::push_into_stack for integers
2024-02-03 21:32:49 +00:00
f5982bc204
Add inline to FromLua<bool>::from_stack
2024-01-27 14:40:32 +00:00
512921404c
Add fastpath push_into_stack/from_stack methods for bool type
2024-01-26 14:07:56 +00:00
df778b7b33
Impl Into/FromLua for OwnedString
2024-01-25 18:04:55 +00:00
2ac7b23596
Impl Into/FromLua for OwnedThread
2024-01-25 09:34:37 +00:00
8200bee467
Implement IntoLua for ref to String/Table/Function/AnyUserData
...
This would prevent cloning plus has better performance when pushing values to Lua stack (`IntoLua::push_into_stack` method)
2024-01-23 22:14:50 +00:00
727f99ee4d
Implement IntoLua for &RegistryKey
...
This would allow just passing registry keys to arguments with fasttrack to push directly into stack.
2024-01-20 22:04:28 +00:00
5043447f23
Support Luau buffer type and and library.
...
Buffer is an object that represents a fixed-size mutable block of memory and added to Luau 0.601.
See https://luau-lang.org/library#buffer-library for more details.
2023-11-16 12:55:58 +00:00
c062cddd87
Fastpath IntoLua/FromLua for StdString and &str
...
This includes direct push to Lua stack and getting value from Lua stack.
2023-08-03 10:02:20 +01:00
28bcc73f2c
Move impl IntoLua for WrappedFunction to the function.rs file
2023-07-27 15:19:34 +01:00
7dc6e4c132
Add Error::runtime() helper
2023-07-10 22:41:03 +01:00
c38a1f060b
Various cosmetic changes
2023-07-10 00:04:40 +01:00
b169031d4e
Don't use any metamethods in Table::sequence_values() iterator.
...
This is matches with `Table::pair()` iterator.
Remove `Table::raw_sequence_values()` iterator.
2023-06-26 10:46:59 +01:00
1f0e81c9a1
Add a dedicated type for Luau vector.
...
Refactor existing implementation and add 4-dimensional vectors support.
2023-06-20 13:30:42 +01:00
0fccdfed5c
Fix feature flags for owned types
2023-04-14 01:17:26 +01:00
65e72f39ae
Remove unstable feature flag from Function::wrap/wrap_mut/wrap_async
2023-04-14 00:21:18 +01:00
68b60e2a0a
Add UserDataRef and UserDataRefMut types that implement FromLua
...
and can be used as accessors to underlying `AnyUserData` type.
2023-02-26 21:52:28 +00:00
1d4a135e8e
Add Function::wrap/Function::wrap_mut/Function::wrap_async to wrap functions into a type that implements IntoLua trait.
...
This is useful to avoid calling `lua.create_function*` every time when `Function` handle is needed.
2022-12-22 16:24:35 +00:00
61c285746c
Remove FromLua impl for UserData+Clone
2022-12-20 23:30:18 +00:00
a13c188de3
Rename ToLua/ToLuaMulti -> IntoLua/IntoLuaMulti
2022-12-19 23:00:47 +00:00
c60f633a62
Add "unstable" feature flag.
...
Hide owned types under the new feature flag.
Drop OwnedString/OwnedThread types (unlikely they are useful).
2022-12-19 22:26:44 +00:00
bf79d9e75d
Initial implementation of owned Lua types
2022-12-18 00:35:41 +00:00
a05a58b258
Update integer/number coercion logic
2022-05-30 19:26:12 +01:00
99becdb590
More inline attributes
2022-05-29 20:17:09 +01:00
3a9c8c2da2
Add Luau vector datatype support
2022-03-22 21:14:06 +00:00
1b74c89509
More performance optimizations
2021-11-25 11:16:12 +00:00
d0641d812f
Refactor a bit conversion int->number
2021-11-04 13:15:26 +00:00
d88a4282c7
Replace macro-based implementation ToLua for arrays to const generics
2021-11-04 00:59:39 +00:00
c8c64a1b5a
Add serializing i128/u128 types.
...
Fixes #81 .
2021-10-04 23:20:11 +01:00
ee1c8a1a3d
Add inline attributes to few hot funcs
2021-09-28 16:19:29 +01:00
24bbd62564
Fix converting Lua sequence table to HashSet/BTreeSet
2021-06-25 01:49:09 +01:00
2250421438
Fix clippy warnings
2021-05-04 23:42:33 +01:00
4af7bcf0d9
Implement ToLua/FromLua for Box<str> and Box<[T]>
2021-05-03 12:22:11 +01:00
1d9cda10eb
Add ToLua implementation for Cow<str> and Cow<CStr>
2021-02-26 10:23:36 +00:00
b6ff501b8c
Fix numeric types conversion for 32bit lua. Fix #27
2021-01-20 10:46:23 +00:00
c65058a40a
impl ToLua and FromLua for HashSet and BTreeSet
2020-09-27 17:54:47 -07:00
79bfb112aa
Remove redundant lifetimes
2020-05-15 01:48:57 +01:00
9f2d598517
Add clippy check and fix clippy warnings
2020-05-15 01:48:56 +01:00
d366ce0dd4
Scope support (including async)
2020-05-11 02:43:34 +01:00
2bd5c2f6ca
Hide Lua "Send" capability under the optional "send" feature flag
2020-05-11 02:43:34 +01:00
7b0e4b4280
Add Send capability to Lua
2020-05-11 02:43:34 +01:00
d672e19365
Add ToLua implementation for slices and arrays
2020-04-29 16:12:58 +01:00
47e8a80c1c
v0.3.0-alpha.1 with async support
...
Squashed commit of the async branch.
2020-04-17 22:39:50 +01:00
affa85feb0
Backport changes from rlua 0.16 (master branch)
2019-09-29 12:53:13 +01: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
Alex Orlenko