Architecting Neovim Extensions: Moving from Vimscript to LuaJIT
An architectural analysis of Neovim's shift from Vimscript to LuaJIT, focusing on the C-API bridge, memory boundaries, and performance verification.
Loading…
ReadMeFeed / Community knowledge
#luajit
Real questions. Useful conversations. Find the people who know your stack.
neovimArchitecting the Neovim Lua API: Bridging C Core and Scripting
An analysis of the Neovim Lua API architecture, exploring the C-to-Lua bridge, trust boundaries, and the embedded LuaJIT VM.
Architecting Neovim Extensions: The C-to-Lua Bridge
Explore the architecture of Neovim's C-to-Lua bridge, detailing how the dispatcher manages the boundary between high-performance core operations and flexible plugin extensibility.
LuaJIT FFI type specialization persists after module reload — how to safely invalidate stale ctype caches
Stale FFI type specialization after reloading a LuaJIT module I am working with LuaJIT's FFI and have run into a design question around type-specialization caching. When a module is reloaded via require (for example after redefining a C struct layout), the recorded type specialization appears to persist, so conversions may still follow the old struct layout.
lua