X-Git-Url: https://git.ralfj.de/rust-101.git/blobdiff_plain/bc32a4e74aa950d3bebf0928d8e7f8b49bdb57c1..393ceeb96e6ad24a36d10c0dd2dc67cede3da47e:/src/part05.rs

diff --git a/src/part05.rs b/src/part05.rs
index 8a2cd90..adbe5c7 100644
--- a/src/part05.rs
+++ b/src/part05.rs
@@ -47,7 +47,8 @@ impl BigInt {
         }
     }
 
-    // We can convert any vector of digits into a number, by removing trailing zeros. The `mut`
+    // Any vector of digits, which meets the structure of BigInt's `data` field, can be easily
+    // converted into a big number just by removing trailing zeros. The `mut`
     // declaration for `v` here is just like the one in `let mut ...`: We completely own `v`, but Rust
     // still asks us to make our intention of modifying it explicit. This `mut` is *not* part of the
     // type of `from_vec` - the caller has to give up ownership of `v` anyway, so they don't care anymore
@@ -147,4 +148,4 @@ fn work_on_variant(mut var: Variant, text: String) {
 //@ I hope this example clarifies why Rust has to rule out mutation in the presence of aliasing *in general*,
 //@ not just for the specific case of a buffer being reallocated, and old pointers becoming hence invalid.
 
-//@ [index](main.html) | [previous](part04.html) | [raw source](https://www.ralfj.de/git/rust-101.git/blob_plain/HEAD:/workspace/src/part05.rs) | [next](part06.html)
+//@ [index](main.html) | [previous](part04.html) | [raw source](workspace/src/part05.rs) | [next](part06.html)