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

Consider using the allocator_api crate #2

Closed
fitzgen opened this issue Nov 29, 2018 · 2 comments
Closed

Consider using the allocator_api crate #2

fitzgen opened this issue Nov 29, 2018 · 2 comments

Comments

@fitzgen
Copy link
Owner

fitzgen commented Nov 29, 2018

Instead of forking from libstd directly ourselves.

This would involve merging String upstream into that crate plus any other collections we might end up needing.

@glandium
Copy link

Note that I'm open to having more collections in the allocator_api. I didn't come to it because I didn't need them yet.

@glandium
Copy link

Also note that the last published version is behind recent API changes to libstd, but I updated master recently.

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

No branches or pull requests

2 participants