Hi Danlogs, Nice explanation but i would recommend one thing to show output automatically without cargo run , install cargo watch and run he command - cargo watch -q -c -x 'run -q' It will save your time in video too.
3:50 Wouldn't n3.clone() work just as well as Rc::clone(&n3) ? The first looks a little cleaner to me. But is there a reason to prefer the second form?
They're equivalent in terms of functionality, but some may argue that one could be more readable than the other (i.e., 𝚁𝚌::𝚌𝚕𝚘𝚗𝚎(&𝚗𝟹) is clearer in its intent of simply creating a shared reference and not a deep clone the data as .𝚌𝚕𝚘𝚗𝚎() sometimes does.)
![AsRef/Borrow Traits, and the ?Sized Marker - Rust [Video Request]](http://i.ytimg.com/vi/4YAmpHMl1Z0/mqdefault.jpg)
![AsRef/Borrow Traits, and the ?Sized Marker - Rust [Video Request]](/img/tr.png)
Hi Danlogs, Nice explanation but i would recommend one thing to show output automatically without cargo run , install cargo watch and run he command - cargo watch -q -c -x 'run -q'
It will save your time in video too.
Great explanation! Thank you :)
Great insights, thanks!
Nice explanation!!!
Thanks for the great video! I hope you have a great rest of your day
consider use nerd fonts so the unicode before master will show. Also, try rust-analyzer. :)
Thanks for the suggestions~ I normally do use them, but this is a new computer and I didn't notice them missing until after the recording 😅
the future ruiner of JavaScript, I love it!
3:50 Wouldn't n3.clone() work just as well as Rc::clone(&n3) ? The first looks a little cleaner to me. But is there a reason to prefer the second form?
They're equivalent in terms of functionality, but some may argue that one could be more readable than the other (i.e., 𝚁𝚌::𝚌𝚕𝚘𝚗𝚎(&𝚗𝟹) is clearer in its intent of simply creating a shared reference and not a deep clone the data as .𝚌𝚕𝚘𝚗𝚎() sometimes does.)
You are passing Referenced to the RC.... Wouldn't just using references work in the original code without the RC