@nick_r_cameron wrote some guides ages ago.
-
-
-
https://github.com/nrc/r4cppp/blob/master/README.md … But it is old and incomplete. I would probably recommend just reading the official book.
-
Thanks! This should be a good starting point, I think. (Just FYI, I was looking for the reverse guide: I have plenty of Rust experience, but minimal C++ experience (I can sometimes make sense of templatized code))
End of conversation
New conversation -
-
-
I would recommend reading Effective C++ and Effective Modern C++ (both by Scott Meyers) once you've gone over the basics. But here are some small tips: 1/n
-
C++ is mut by default, copy by default (moves are done with std::move) Templates (like generics, but less control, more flexibility) are evaluated by replacing types in the dining body and then trying to compile, rather than verifying if the types 2/n
-
Satisfy some interface (coming in the future with something called concepts, but it's very different from how you'd think of Traits working). Reading template errors is a skill because of the above. Skip all lines that are not your code, then try to figure out why the line 3/n
-
You wrote isn't compatible with that template. (This is one of the most painful parts of C++ in my opinion) Rust -> C++ std:: Box<T> -> std::unique_ptr<T> std::rc::Rc<T> -> std::shared_ptr<T> Constructors have a lot of rules for when they are implicitly defined, kind of 4/n
-
like how the Copy trait can only be applied to types that only contain Copy types, but with extra rules due to handling backwards compatibility and moves being added later on. There's a ton more, but the details can get really nuanced. Go slow, in my opinion C++ is 5/n
-
Harder to grok because the smallest change in syntax can have a big impact on the meaning of the code (Rust can too, but C++ has more special cases). Good luck!
End of conversation
New conversation -
-
-
I've been meaning to write one some day but I never get around to it
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I did a simple intro a while ago. http://nercury.github.io/c++/intro/2017/01/22/cpp-for-rust-devs.html …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
just put the types before the names instead of after, and don't forget to free what you allocate. simple! :D
-
I believe that's just plain C.

-
ok delete what you new
End of conversation
New conversation -
-
-
Template is usually fawned upon on unless absolutely necessary (e.g., numeric libraries). Google C++ Style Guide is a good pointer on what features to steer clear from.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I don’t think *anyone* can ever safely say that they are competent in C++
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If you come from C originally, https://ds9a.nl/articles/posts/cpp-intro/ … might be useful to you.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You don't want C++. There are lots of concepts that are missing in C++.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Meme: no one is actually really completely competent in C++. Don’t push too hard.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.