3 ms·
Not OP, but as someone who theoretically would like Rust - I'll bite. Maybe my usecase is a common one. I understand memory management in C. I understand it mo
by lacampbell 10y ago
Not OP, but as someone who theoretically would like Rust - I'll bite. Maybe my usecase is a common one.
I understand memory management in C.
I understand it modern C++ (destruction when going out of scope, smart pointers etc).
Basically, a description and discussion of borrow-checking for people who have already used system programming languages would be really helpful. I feel like the book is targeting people who have only used garbage collected languages.
Or is the memory management of rust so novel it can't be described in those terms? I find the concepts aren't very concrete to me.
- fuine 10y agoHave you tried looking at https://github.com/nrc/r4cppp https://github.com/nrc/r4cppp ?
- lacampbell 10y agoThat looks like exactly what I'm after actually. I'll read this next time I try rust.
- steveklabnik 10y agoIt's trying to be accessible to those people, but not strictly for them. I don't think the issue here is that it's for GC'd users, but that it's trying to explain things from whole-cloth, where you're looking for a direct comparison, "c does this, rust does that." I try generally to keep other languages out of Rust's docs for various reasons, but agree that these kinds of resources are useful; I wrote "Rust for Rubyists" after all! I'm hoping that others will step in and fill this gap; the repo in my sibling is a great start.