Visen

I believe the std reader and writer have been restructured now to be proper interfaces

> What are the 'proper interfaces' you mention? Interfaces meaning a struct containing a `*anyopaque` and a function pointer. This is how `std.mem.Allocator` is implemented. Zig now has a [proper...

> @VisenDev Your link doesn't return any result, did you mean https://ziglang.org/documentation/master/std/#std.io.AnyReader? Zig recently changed the autodoc code. That must have broken my link

My motivation for this is I think at a bare minimum we should be able to tell the user why something fails. If parsing fails, I think it should have...

My implementation of autoPushFunction automatically does this. ```zig if (@typeInfo(info.Fn.return_type.?) == .ErrorUnion) { const result = @call(.auto, function, parameters) catch |err| { lua.raiseErrorStr(@errorName(err), .{}); }; lua.pushAny(result); } else { const...

I think Luajit is still a WIP right now

@natecraddock I think some nice zig integration for [luajit ffi](https://luajit.org/ext_ffi.html) would be amazing if we could get that to work It would make it so nice to use lua with...

This stack segmentation fault is also happening when attempting to parse large json strings using `std.json.parseFromSlice` Example code causing a segfault. `level.Level` is a large struct. ``` const string =...

I second these changes

> The solution would be having people with specialist knowledge paired up to the topic of the prompts. I intentionally create very complex and difficult prompts so that the model...