Skip to content

Allocator interface for memory pool #16

Description

@Ahajha

It would be useful to be able to use memory pools in existing containers, like std::vector, std::deque, etc. (Along with their std::pmr::* counterparts). To do this, we would need an allocator that "wraps" the memory pool.

I'm thinking there should be two versions, one with user-managed pools (so a reference to the host allocator would need to be stored in the container, allows flexibility at the cost of a bit of extra memory), and another with a global pool (less memory usage, less flexibility).

If I were to work on such a feature, should I fork the dev branch and work from there? What is the preferred contributing method?

(Btw, hi from reddit!)

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions