Rust Programming Cookbook

How to do it...

Understanding shared ownership only requires eight steps:

1. In the fairly young ecosystem that is Rust, APIs and function signatures are not always the most efficient, especially when they require somewhat advanced knowledge of memory layout. So, consider a simple length function (add it to the mod tests scope):

    ///     /// A length function that takes ownership of the input     /// variable    ///     fn length(s: String) -> usize {        s.len()    } 

While unnecessary, the function requires that you pass your owned variable to the scope.

2. Luckily, the clone() function is ready for you if you still need ownership after the function call. This is similar to a loop, by the way, where ownership is moved in the first iteration, which means it ...