refactor(furvm): cleanup things #62

New Issue

2026-08-14T23:24:43Z

CHatingPython commented

2026-08-14 23:24:43 +00:00

Furvm is haunted by my rushed and quite frankly stupid decision of implementing the handle system. Removal of handles, naturally, calls for a better system for allocating and deallocating things. The current solution of keeping everything in their respective vectors is temporary, as it is (at least I think) unsustainable in the long run.

My proposal is:

to scrap the things allocator completely and replace it with the default C++ allocator.
Add a dedicated collection of heap-allocated things to the context.
Use a custom allocator for things on the stack.

Furvm is haunted by my rushed and quite frankly stupid decision of implementing the handle system. Removal of handles, naturally, calls for a better system for allocating and deallocating things. The current solution of keeping everything in their respective vectors is temporary, as it is (at least I think) unsustainable in the long run. My proposal is: 1. to scrap the things allocator completely and replace it with the default C++ allocator. 2. Add a dedicated collection of heap-allocated things to the context. 3. Use a custom allocator for things on the stack.

CHatingPython added this to the v0.6.7 milestone 2026-08-14 23:24:43 +00:00

CHatingPython added the Kind/Enhancement

Priority

Critical

1

labels 2026-08-14 23:24:43 +00:00

CHatingPython self-assigned this 2026-08-14 23:24:43 +00:00

CHatingPython added this to the furvm project 2026-08-14 23:24:43 +00:00

CHatingPython moved this to To Do in furvm on 2026-08-14 23:24:45 +00:00

CHatingPython moved this to In Progress in furvm on 2026-08-15 09:55:11 +00:00

CHatingPython referenced this issue from a commit

2026-08-15 20:16:59 +00:00