A dev build is to name the raylib resources still loaded at exit

This commit is contained in:
Joseph Ferano 2026-09-25 09:43:52 +07:00
parent 836185a174
commit af4da764b2

View File

@ -1686,7 +1686,8 @@ Precision over completeness: a site that does not allocate is never marked, and
=vec-new=, =map-new=, dyn arithmetic, keywords and dyn push and put are
deliberately silent, each for its own reason.
** TODO A debug tracking allocator over the raylib boundary
** NEXT A debug tracking allocator over the raylib boundary
Decided 2026-09-25: build it. A dev build counts loads against unloads in the generated wrappers and lists what is still held at exit, by type and load site. Release builds pay nothing.
ASan's leak detection covers memory instrumented code allocated — the Flan
allocator, already clean. It does not cover a leaked texture, because that memory
belongs to uninstrumented raylib. Every raylib call goes through a generated