-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make auto allocators optional #1
Comments
for constructors and raylib functions that allocate you can now specify your own arena allocator. the only auto arena is when converting string arguments to function calls. i guess this should be replaced by: if function call is one that has string arguments:
performance impact of all this is probably so tiny it's not a priority |
The auto arena for string arguments does actually reduce bunnymark by 4000 when using DrawText()! Another alternative: allocate temp memory once on startup and then re-use it. not threadsafe. might need custom arena/allocator or something. |
local arena for string arguments done |
make sure advanced users have option to specify their own allocators to improve performance - the auto ones should not be mandatory anywhere
The text was updated successfully, but these errors were encountered: