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

Make pool allocations more explicit #3387

Closed

Conversation

ncesario-lunarg
Copy link
Collaborator

This removes the ability for some classes to be implicitly allocated using the pool allocator. Now NewPoolObject should be used to explicitly allocate any object using the pool allocator.

Some other things this change does:

  • Remove some of the NewPool* non-generic functions, replacing them with a single "make_unique" style function.
  • Existing pointers allocated with the standard allocator are replaced with smart pointers.

@ncesario-lunarg ncesario-lunarg force-pushed the explicit-pool-alloc branch 2 times, most recently from f04b514 to 70493be Compare December 9, 2023 06:53
This removes the ability for some classes to be implicitly allocated
using the pool allocator. Now NewPoolObject should be used to explicitly
allocate any object using the pool allocator.

Some other things this change does:
- Remove some of the NewPool* non-generic functions,
  replacing them with a single "make_unique" style function.
- Existing pointers allocated with the standard allocator are replaced
  with smart pointers.

Related to KhronosGroup#3123.
@arcady-lunarg
Copy link
Contributor

I think we're going to take a different approach here, plus this isn't really a priority at the moment.

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

Successfully merging this pull request may close these issues.

2 participants