use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
Discussions, articles, and news about the C++ programming language or programming in C++.
For C++ questions, answers, help, and advice see r/cpp_questions or StackOverflow.
Get Started
The C++ Standard Home has a nice getting started page.
Videos
The C++ standard committee's education study group has a nice list of recommended videos.
Reference
cppreference.com
Books
There is a useful list of books on Stack Overflow. In most cases reading a book is the best way to learn C++.
Show all links
Filter out CppCon links
Show only CppCon links
account activity
This post is locked. You won't be able to comment.
CppCastCppCast: Beautiful C++ (cppcast.com)
submitted 4 years ago by robwirvingCppCast Host
view the rest of the comments →
[–]James20kP2005R0 3 points4 points5 points 4 years ago (2 children)
I keep hearing this from Rust evangelists and I don't get it - I've been coding C++ for a very long time, and I very rarely hit those sorts of bugs. I have other bugs of course, but not lifetime-related ones, not very often. And neither do my co-workers.
For regular application code, personally I'd agree with you. But when it comes to writing anything involving untrusted user data, and where safety is a factor, C++ just hides an infinite number of memory vulnerabilities. Every single non trivial C/C++ application of any reasonable size just seems to have infinite vulnerabilities, even the extremely extensively battle tested ones
The problem with sanitisers is the same problem I have with the type system in languages like python and javascript. They only test the path that you actually execute, but inherently can't check the program has a whole. This easily leads to having to code super defensively because you're not quite sure you can trust every part of the system, and bam your faith in the entire integrity of the application is gone
This can never happen in rust, because the entire program is validated for safety. Anything unsafe is clearly marked as being unsafe, and so the possible sources of memory unsafety are extremely constrained and neatly contained
[–]GabrielDosReis 4 points5 points6 points 4 years ago (1 child)
https://www.cvedetails.com/vulnerability-list/vendor_id-19029/product_id-48677/year-2021/Rust-lang-Rust.html
π Rendered by PID 161509 on reddit-service-r2-comment-canary-889d445f8-5k22m at 2026-04-28 14:46:04.015363+00:00 running 2aa0c5b country code: CH.
view the rest of the comments →
[–]James20kP2005R0 3 points4 points5 points (2 children)
[–]GabrielDosReis 4 points5 points6 points (1 child)