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.

Sign up for GitHub

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

Jump to bottom

Rework async_allocator #45

Open
maikel opened this issue Jun 28, 2023 · 1 comment
Open

Rework async_allocator #45

maikel opened this issue Jun 28, 2023 · 1 comment
Labels
discussion sequence senders

Comments

@maikel
Copy link
Owner

maikel commented Jun 28, 2023

I've discussed the async_allocator with kirk and its probably better to not give out senders to raw memory allocation but instead to async_new and async_delete which does both, allocation/construction and deallocation/destroy.
@maikel
Copy link
Owner Author

maikel commented Jun 28, 2023

We could also use some kind of memory handle to automatically delete the constructed object upon leaving an using-scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion sequence senders
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@maikel