Update to `mlua` `v0. 12.0` ?

[c-c-k]

Hello, sorry to bother, are you planning to update nvim-oximlua to the newly released mlua v0.12.0 in the near future?

[Tired-Fox]

I can definitely take a look. If it isn't too involved to update, I can get it out today.

I don't currently use mlua very often at the moment. I didn't see there was an update.

No bother at all, thank you for bringing this to my attention.

[c-c-k]

Thank you very much, there's no rush, I just noticed the update a short while ago myself.

[Tired-Fox]

Looks to not be too bad for updates. Main focus will be to update the derive macros to mimic Mlua's new derive macros, along with removing the UserData one in favor of Mlua's. There may be some typing info to update with the new integer64 luau support.

Since I may take this time to update or rewrite the derive macros I will have this done by next week. But I imagine I will have it done sooner.

[c-c-k]

That is fast, considering the 🐌 pace of my own progress I think I'll go hide under a blanket now.
Thank you very much again.

[Tired-Fox]

@c-c-k

I believe I have something working. I basically copied what mlua was doing for their derive macro. Some other changes have occured and the macro may not be as expressive or powerful, but that is to keep it close to the functionality of mlua's derive macro.

If you wanted to try it out early you can use the main branch. Otherwise, I will probably keep polishing and release a new version to crates at the end of the week.

[c-c-k]

Wow, you're fast, for the moment I've switched to trying to fix my broken NVIM config with just Lua to get a clearer base state to translate into mlua-extras (and posibly lux/rocks.nvim lux rewrite), so after rushing you I end up lagging behind myself, sorry.

Losing some of your macro's power is sad but essential to stay in line with mlua I guess.
Also, I don't have much experience with writing macros so this might be a stupid question, but, rather than copying the mlua macro wouldn't it make sense to delegate to it instead?

[Tired-Fox]

So I rewrote it almost 1-to-1 so I can add additional features like getting param names and doc comments. I also switched to using the Typed trait variants.

Unfortunately there isn't a good way to make it auto impl UserData or to reuse mlua-derive crates features since it is a proc-macro crate.

[Tired-Fox]

No worries about rushing. I'm just working at my pace. Hope this crate continues to be useful to your project(s)

[c-c-k]

Unfortunately there isn't a good way to make it auto impl UserData or to reuse mlua-derive crates features since it is a proc-macro crate.

Because a derive macro can only add code and thus can't insert another macro into the derives list for a type 😕
SIGH This might a serious road-blocker to the idea of a 'DualConfig' and 'DualApi' macros that would split a single Config/Api userdata into a type that would be convenient to use Rust side (and would have Rust side docs) and a userdata (or table) that would be convenient to use Lua side (and would have Lua side docs), but that's a separate topic (that I hope I could have your consultation on when I get to trying to implement it).

Thank you very much again 🙏