How ref qualifiers led to deducing this
A follow up on last weeks post on ref qualifiers: How ref qualifiers led to deducing this by Jens Weller From the article: Last week I shared an overview on ref qualifiers with you, this is a follow…
Read the full articleYou might also wanna read
C++ Constants Explained: When to Use #define, const, and constexpr
A technical guide published on DEV Community breaks down the three main ways to define constants in C++: #define, const, and constexpr. The
C++26's std::is_within_lifetime: Checking Object Lifetime During Constant Evaluation
When I was looking for the next topic for my posts, my eyes stopped on std::is_within_lifetime. Dealing with lifetime issues is a quite comm
sandordargo.com·4mo ago
Examining Destructive Move Semantics in C++26: Can Programmers Express Object-Consuming Functions?
Can I express a function that consumes an object? Meaning that its destructor is not run on the moved-from object? Like the proposed library
stackoverflow.com·7mo ago
C++ Standard Library's Fifteen-Year Evolution Away from std::function
# The C++ standard library has been walking itself back for fifteen years, and the receipts are public Sandor Dargo's [post this month on `s
hftuniversity.com·1mo ago
Benchmarking enum-to-string conversion: C++26 reflection vs traditional approaches
Article/tutorial on
vittorioromeo.com·2mo ago
Defensive Programming Patterns in Rust: When "This Should Never Happen" Actually Does
I have a hobby. Whenever I see the comment // this should never happen in code, I try to find out the exact conditions under which it could
corrode.dev·7mo ago
Comments
Sign in to join the conversation.
No comments yet. Be the first.