diff options
| author | Cesar Eduardo Barros <cesarb@cesarb.eti.br> | 2017-01-19 22:45:57 -0200 |
|---|---|---|
| committer | Cesar Eduardo Barros <cesarb@cesarb.eti.br> | 2017-01-19 22:45:57 -0200 |
| commit | c7b092b47d8e50b58c975040af0a84a544f7fa7a (patch) | |
| tree | 3226fb2c8b70a559dc812f85d14435e92fabfbff | |
| parent | 465d24e1a03f21c1c7685f5105a32ffc52bdd68c (diff) | |
No need to mention how these fields are used
| -rw-r--r-- | src/doc/book/trait-objects.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/src/doc/book/trait-objects.md b/src/doc/book/trait-objects.md index 71536f409e8..00a841a75db 100644 --- a/src/doc/book/trait-objects.md +++ b/src/doc/book/trait-objects.md @@ -263,8 +263,7 @@ any resources of the vtable’s type: for `u8` it is trivial, but for `String` i will free the memory. This is necessary for owning trait objects like `Box<Foo>`, which need to clean-up both the `Box` allocation as well as the internal type when they go out of scope. The `size` and `align` fields store -the size of the erased type, and its alignment requirements; these are -used by the `std::mem::size_of_val` and `std::mem::align_of_val` functions. +the size of the erased type, and its alignment requirements. Suppose we’ve got some values that implement `Foo`. The explicit form of construction and use of `Foo` trait objects might look a bit like (ignoring the |