The common scenario for f and g to consume x is that x is a smart pointer type e.g. Rc/Arc.
to make it clear that the clone is "cheap", some Rust developer prefer using `Arc::Clone(&x)` over `x.clone()`.
to make it clear that the clone is "cheap", some Rust developer prefer using `Arc::Clone(&x)` over `x.clone()`.
No comments yet.