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
Any plans on allowing more flexible support for custom heap allocations through bumpalo or the official WIP allocator API? It is a bummer that if you write your game's looping code using bumpalo containers and want to do pathfing within the main game loop's lifecycle, you cannot use the the bumpalo bump allocator for the heap allocations created by pathfind's functions.
The text was updated successfully, but these errors were encountered:
That would require an incompatible API, but if someone proposed a well-thought new API, why not? I have no need for it myself so I am unlikely to do the work on my side as I would not be a user of this API.
I will look into this at some point, or I will just copy the code from this crate locally and write appropriate variations to it for my own use. I am no expert on the subject, but it would certainly help to get the official allocator API stabilized first and see how it is getting utilized in practice by other crate maintainers, but there is no guarantee how long will that take, 5 years? There's a good post on this topic talking about how you currently have various ways to implement it.
Hello,
Any plans on allowing more flexible support for custom heap allocations through bumpalo or the official WIP allocator API? It is a bummer that if you write your game's looping code using bumpalo containers and want to do pathfing within the main game loop's lifecycle, you cannot use the the bumpalo bump allocator for the heap allocations created by pathfind's functions.
The text was updated successfully, but these errors were encountered: