Skip to content
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

Bumpalo or Allocator API support? #602

Open
kaphula opened this issue Sep 20, 2024 · 2 comments
Open

Bumpalo or Allocator API support? #602

kaphula opened this issue Sep 20, 2024 · 2 comments

Comments

@kaphula
Copy link

kaphula commented Sep 20, 2024

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.

@samueltardieu
Copy link
Collaborator

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.

@kaphula
Copy link
Author

kaphula commented Sep 23, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants