You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Internally, kaguya uses a lot of std::string, std::vector, and such, when sending data between C++ and Lua.
I would like to be able to customize the allocator used for that memory.
Currently, I have to hook the system-wide malloc/free functions, which is rather brittle.
Note: this is not the Lua allocator (for inside-the-VM allocations), which is already customizable via the Stateconstructor.
The text was updated successfully, but these errors were encountered:
Internally, kaguya uses a lot of
std::string
,std::vector
, and such, when sending data between C++ and Lua.I would like to be able to customize the allocator used for that memory.
Currently, I have to hook the system-wide
malloc
/free
functions, which is rather brittle.Note: this is not the Lua allocator (for inside-the-VM allocations), which is already customizable via the
State
constructor.The text was updated successfully, but these errors were encountered: