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

Rename Alloc trait to Allocator in README #85

Merged
merged 1 commit into from
Feb 12, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
This WG aims to:

* Define traits and other APIs for memory allocators,
with the unstable [`std::alloc::Alloc`] trait as a starting point.
with the unstable [`std::alloc::Allocator`] trait as a starting point.

* Make collections such as `Vec<T>` able to use any allocator,
most likely through an additional type parameter.
Expand All @@ -22,7 +22,7 @@ For lower-latency discussion, we have the [`t-libs/wg-allocators`] stream on Zul
To try out different proposals, [Tim](https://github.com/TimDiekmann) has created a crate at [TimDiekmann/alloc-wg](https://github.com/TimDiekmann/alloc-wg). For more information on this consult the [readme](https://github.com/TimDiekmann/alloc-wg/blob/master/README.md).


[`std::alloc::Alloc`]: https://doc.rust-lang.org/1.34.0/std/alloc/trait.Alloc.html
[`std::alloc::Allocator`]: https://doc.rust-lang.org/std/alloc/trait.Allocator.html
[RFC #1398]: https://github.com/rust-lang/rfcs/pull/1398 "Allocators, take III"
[tracking issue #32838]: https://github.com/rust-lang/rust/issues/32838 "Allocator traits and std::heap"
[tracking issue #42774]: https://github.com/rust-lang/rust/issues/42774 "Tracking issue for custom allocators in standard collections"
Expand Down