From: Alexander Krotov Date: Thu, 15 Sep 2016 00:32:17 +0000 (+0300) Subject: s/implemenets/implements/ X-Git-Url: https://git.ralfj.de/rust-101.git/commitdiff_plain/61b95423bc993e91dc64dd022321041fca3af9cc?hp=-c s/implemenets/implements/ --- 61b95423bc993e91dc64dd022321041fca3af9cc diff --git a/src/part11.rs b/src/part11.rs index 9d931db..5134401 100644 --- a/src/part11.rs +++ b/src/part11.rs @@ -23,7 +23,7 @@ struct CallbacksV1 { //@ But, Rust complains about this definition. It says something about "Sized". What's the trouble? See, for many things we want to do, it is crucial that //@ Rust knows the precise, fixed size of the type - that is, how large this type will be when represented in memory. For example, for a `Vec`, the //@ elements are stored one right after the other. How should that be possible, without a fixed size? The point is, `FnMut(i32)` could be of any size. -//@ We don't know how large that "type that implemenets `FnMut(i32)`" is. Rust calls this an *unsized* type. Whenever we introduce a type variable, Rust +//@ We don't know how large that "type that implements `FnMut(i32)`" is. Rust calls this an *unsized* type. Whenever we introduce a type variable, Rust //@ will implicitly add a bound to that variable, demanding that it is sized. That's why we did not have to worry about this so far.
//@ You can opt-out of this implicit bound by saying `T: ?Sized`. Then `T` may or may not be sized.