-
Notifications
You must be signed in to change notification settings - Fork 478
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issues of Lua binding #2474
Comments
Hi, do you how to release a lua package that contains a C dylib? |
Seems users who depend on opendal-ruby will need to build opendal by themselves? For example: https://github.com/openresty/lua-cjson/blob/master/lua-cjson-2.1.0.12-1.rockspec |
Yeah, luarocks neet to mannel execute |
https://luarocks.org/ supports binary release like pypi does? |
Another question is about the support for Lua's async operations. In Lua scenarios such as OpenResty, pure asynchronous operations are required. There doesn't seem to be a good way to make Rust's asynchronous IO work in OpenResty. |
There are few solutions how to integrate tokio (for example) with openresty. I also have plans to build a bridge between openresty (and libuv) and mlua async functionality. |
In openresty world, it has a bridge implement named as https://github.com/kingluo/lua-resty-ffi, it support offload all other runtime to other thread, and using eventfd notify nginx worker epoll to resume lua coroutine, I think it was a good solution to mlua async functionality |
Tasks
The text was updated successfully, but these errors were encountered: