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

Investigate doing an allocator #5

Open
burdges opened this issue Jan 12, 2017 · 3 comments
Open

Investigate doing an allocator #5

burdges opened this issue Jan 12, 2017 · 3 comments

Comments

@burdges
Copy link
Owner

burdges commented Jan 12, 2017

I think complex data structures like say Vec<T> can be done most easily using an allocator that wraps the standard allocator. It's seems needlessly complex to write a whole ZeroDropVec<T> just to avoid writing an allocator

@vks
Copy link

vks commented Jan 12, 2017

Actually there is already such a vector type on crates.io: cryptovec

@burdges
Copy link
Owner Author

burdges commented Jan 13, 2017

Wonderful, thank you! Allocators do still sound interesting, but they can lead to mistakes easily too.

@burdges burdges closed this as completed Jan 13, 2017
@burdges
Copy link
Owner Author

burdges commented Jan 13, 2017

In fact, I'll leave this open since an allocator is still interesting for various reasons.

@burdges burdges reopened this Jan 13, 2017
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