-
Notifications
You must be signed in to change notification settings - Fork 57
Description
See #153 for previous discussion. Opening this issue for discussion a few specifics.
Current status of supporting 0.14 and 0.15 in main, as of ziglua commit 317bfbe:
- Tests work fine for Lua 5.2, 5.3, 5.4. E.g.,
zig build -Dlang=lua54 test
runs fine.- The "new"
.c
calling convention (as opposed to.C
) works already in zig 0.14.
- The "new"
- The interpreter sample doesn't work on zig 0.15 because of the Io changes. I think it can be adapted to work on both.
- Lua 5.1 is broken because of the file patching changes. I imagine the patching code could be fixed to support both. Or alternatively, CI could also not test Lua 5.1 on zig 0.14.
- Personally I use Lua 5.4, so I wouldn't care if Lua 5.1 doesn't work zig 0.14. But it may be an annoying surprise to someone else.
The amount of breakage due to 0.15 is at this point fairly minor. IMO there's a LOT of value in supporting the latest stable Zig (0.14) as many projects are on that (f.ex. Ghostty, flow). There's arguments to be made for both sides on whether to work on applications and projects using zig-0.14 (stable) or keep everything up to date with Zig nightlies. However, what sucks from the Ziglua's perspective is that suppose I'm working on say a game project, and find that Ziglua added some nice new feature (lua update or new lua version for example), and I'd like to update Ziglua to get that feature. Well, if Ziglua main only works with Zig nightlies, I'd have to port my whole game codebase to Zig nightly just to update one library.