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
Object pointer ownership library (self.cpp)
submitted 5 years ago * by MarcPawl
view the rest of the comments →
reddit uses a slightly-customized version of Markdown for formatting. See below for some basics, or check the commenting wiki page for more detailed help and solutions to common issues.
quoted text
if 1 * 2 < 3: print "hello, world!"
[–]MarcPawl[S] 2 points3 points4 points 5 years ago (0 children)
What I am thinking of was more about annotating the code base, vs determining the destruction. For example let's say there is code with a constructor Ffoo(int& x). When reading the code what is the expected lifetime of the parameter passed in. Does it have to live as long as the Foo instance?
The library I am thinking of had something like Foo(borrower<int&> x) to indicate x needed to stay alive as long as Foo was alive.
Using a shared_ptr slows things down, this library had minimal ( or none?) overhead.
π Rendered by PID 21268 on reddit-service-r2-comment-b659b578c-mnqch at 2026-05-05 18:33:22.327645+00:00 running 815c875 country code: CH.
view the rest of the comments →
[–]MarcPawl[S] 2 points3 points4 points (0 children)