Skip to content
This repository was archived by the owner on Nov 27, 2020. It is now read-only.

Commit e47c919

Browse files
committed
Update README
1 parent e403409 commit e47c919

File tree

1 file changed

+1
-8
lines changed

1 file changed

+1
-8
lines changed

README.md

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -37,10 +37,7 @@ Changes regarding the current `Alloc` trait
3737

3838
- Added an associative error type to [`AllocRef`]. Besides adding the possibility of returning additional information on
3939
allocation failure, it's also possible to split the usage of the [`AllocRef`] into a fallible and an infallible case.
40-
Personally I think this is a pretty big deal, as kernel programmer can rely on allocation, which will never fail. If
41-
an allocation can fail, only a `try_*_in` method may be available. To maintain backwards compatibility, [`AbortAlloc`]
42-
was introduced. [`AbortAlloc`] wraps another allocator, but aborts on OOM thus `AbortAlloc<Global>` may be used as
43-
default allocator for [`Box`] or `Vec`. To realize this, [`AbortAlloc`] implements `AllocRef<Error=!>`.
40+
Personally I think this is a pretty big deal, as kernel programmer can rely on allocation, which will never fail.
4441

4542
Issue: [rust-lang/wg-allocators#23](https://github.com/rust-lang/wg-allocators/issues/23)
4643

@@ -55,10 +52,6 @@ Changes regarding the current `Alloc` trait
5552

5653
Issue: [rust-lang/wg-allocators#5](https://github.com/rust-lang/wg-allocators/issues/5)
5754

58-
- Add support for `_zeroed` buffer in `Vec`.
59-
60-
Issue: [rust-lang/wg-allocators#32](https://github.com/rust-lang/wg-allocators/issues/32)
61-
6255
Currently associated containers
6356
-------------------------------
6457

0 commit comments

Comments
 (0)