Add lunatik objects to README - #340
sneaky-potato wants to merge 1 commit into
Conversation
Signed-off-by: Ashwani Kumar Kamal <ashwanikamal.im421@gmail.com>
|
|
||
| The lifetime of an object is not tied solely to Lua garbage collection. An object remains alive as long as at least one reference exists. | ||
|
|
||
| Some objects expose an explicit *stop* or *close* operation, which releases internal resources (such as Lua states or kernel hooks) before the object itself is freed. |
There was a problem hiding this comment.
"Lua states" seems misleading here.. see https://www.lua.org/manual/5.4/manual.html#lua_State
|
|
||
| Lua garbage collection may release Lua references to an object, but this does not necessarily destroy the underlying kernel object. Garbage collection typically results in a reference counter decrement. | ||
|
|
||
| Kernel-held references keep the object alive even after all Lua references are gone. For deterministic cleanup, objects should be explicitly stopped or unloaded when appropriate. |
| Lunatik exposes kernel facilities to Lua through *objects*. A Lunatik object is a Lua userdata that represents a kernel-resident resource and is shared between Lua and C code. | ||
|
|
||
| Internally, each Lunatik object combines: | ||
| - a Lua userdata |
There was a problem hiding this comment.
per runtime, right? each object might correspond to many userdata.
|
@sneaky-potato are you still working on this? |
|
Hi @lneto , yes. I’ve been a bit caught up with other work lately, but I haven’t dropped it and will resume once things free up. Thanks for checking! I will mark the PR as draft for now. |
No worries, I'm just planning the next release.. thanks! |
|
Agent comment (Claude Code), posted from @lneto's account.
|
2 participants
Fixes #183