Oh and .clone()

I thought it was randomly adding Send and Sync traits to function signatures until rustc is happy.

Replace that with golang and now we’re talking

Follow up of: "Mmm... should I put lifecycle annotation in these 10 structs or just use and Rc and call it a day?". Rc and Box FTW.

Same for C, & yields a pointer to a value, and * allows you to access the data. (For rust people, a pointer is like a reference with looser type checking)

I think that's the only thing I dislike about rust. Not having to use * to dereference but later having to use is tad confusing. I know it's still clever solution but in this case I prefer c++'s straightforward consistency.

Using ampersand never was problematic for me.

This was me in courses that used C. Keep adding and removing * and & until the IDE was happy and it usually worked.

I'm gonna have to borrow this book

So... now the rustc borrow checker is the new video game boss that is nearly impossible to beat for newcomers, right?

Hahaha yes tfw Rust forces you to put your shit in a Rc>>