Tag
31 posts
Both give you control without a garbage collector. Rust makes memory safety the default; C++ has the larger ecosystem and decades of code. Compare safety, tooling, interop and when to stay in C++.
Go optimizes for a team shipping a service quickly; Rust optimizes for control and correctness. Compare error handling, concurrency, memory, hiring and where each language stops being the easy answer.
Box owns one heap value, Rc shares it on one thread and Arc shares it across threads. See what each costs, when you need RefCell or Mutex too, and how to choose.
A tuple struct with one field costs nothing at runtime and stops you passing a user id where an order id belongs. Learn construction, derives, Deref pitfalls and the orphan rule workaround.
Shadowing re-binds a name with let, even to a new type, while mut changes a value in place. See when each is the right tool and the one trap that surprises people.
String owns its text and str is a borrowed view of text somewhere else. Use that split to pick the right type in function signatures and structs.
Choose between Vec, VecDeque, HashMap, HashSet, BTreeMap and BTreeSet by the operations you need, with complexity, ordering and memory notes.
Closures capture their environment, and the Fn, FnMut and FnOnce traits describe how. See which one the compiler picks and which bound to write.
Iterators are lazy: adapters like map and filter do nothing until a consumer such as collect or sum runs. See the chain, the traits and the common traps.
A package has a Cargo.toml, a crate is one compilation unit, and a module is a namespace inside it. Learn how the three nest and what each one changes.
Modules organize Rust code and control what is public. Learn mod, pub, use, super, self, file layout and why privacy is by module and not by type.
Define a struct, give it methods in an impl block, add associated functions like new, and see tuple and unit structs plus update syntax and derive.