natecraddock / natecraddock/ziglua
Define apicheck function to use a Zig panic
- Dominant language
- Zig
- Stars
- 522
- Forks
- 72
- Avg merge
- 10d 6h
- Merged PRs (30d)
- 1
Description
From a quick glance at the Lua sources, it may be possible to override the use of assert.h for the API check with a custom function. If so, this would make api checks much more easy to debug with zig panics and stack traces.
And while we are here, should we make it possible to define LUA_USE_APICHECK manually (so it can be always on, or on in all safe modes?)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Lua sources and the assert.h path used for API checks, then review linked pull request #213 to understand the work already underway. The scope includes routing API-check failures through a Zig panic and deciding whether LUA_USE_APICHECK can be set manually; completion should resolve both behaviors without leaving the configuration ambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, zig
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100