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

Support custom memory allocation functions #794

Open
me21 opened this issue Aug 5, 2024 · 2 comments
Open

Support custom memory allocation functions #794

me21 opened this issue Aug 5, 2024 · 2 comments
Labels
feature request Request for a new feature help wanted Need outside help

Comments

@me21
Copy link

me21 commented Aug 5, 2024

At the moment, *_create functions use calloc. Please support custom memory (de)allocation functions like zlib-ng does.

@nmoinvaz
Copy link
Member

nmoinvaz commented Aug 5, 2024

Feel free to open a PR.

@nmoinvaz nmoinvaz added help wanted Need outside help feature request Request for a new feature labels Aug 5, 2024
@tbeu
Copy link

tbeu commented Feb 18, 2025

Feel free to open a PR.

This is underspecified:

  • Should it be at configuration-time, compile-time or run-time?
  • If at run-time:
    • Should an additional user payload (opaque) (like in zlib or zlib-ng) be considered or should it be the same API as std::calloc and std::free?
    • Should existing API functions be kept for backwards compatibility or can they be altered?
  • What about realloc?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Request for a new feature help wanted Need outside help
Projects
None yet
Development

No branches or pull requests

3 participants