Releasing the 5th Track for Meeting C++ 2025

By Meeting C++ | Oct 15, 2025 05:24 AM | Tags: meetingcpp community

Meeting C++ hosts a new track in Berlin this year, offering 4 tracks onsite

Releasing the 5th Track for Meeting C++ 2025

by Jens Weller

from the article:

I am excited to announce that with the recent changes to the schedule, Meeting C++ 2025 has now 5 tracks: 4 onsite and 1 online track. This new track is possible thanks to better funding from sponsors and exhibitors enabling even more C++ content at Meeting C++ in Berlin.

For onsite attendees there is a new batch of hotel tickets and team tickets available. The current hotel ticket batch sells until Mid October.
New talks at Meeting C++ 2025

These are the new talks which are now at the conference:

    100 BC (binary compatibility) - Marc Mutz
    Case Study: Purging Undefined Behavior and Intel Assumptions in a Legacy Codebase - Roth Michaels
    Type Traits without Compiler Intrinsics – The Promise of Static Reflection - Andrei Zissu
    Back to the basics: Namespaces 101 - Sandor Dargo
    Building Bridges: C++ Interop., Foreign Function Interfaces & ABI - Gareth Williamson
    Instruction Level Parallelism and Software Performance - Ivica Bogosavljevic
    Real-time Safety — Guaranteed by the Compiler! - Anders Schau Knatten
    Missing (and future?) C++ range concepts - Jonathan Müller
    From Introductory to Advanced C++ - Learning Guidelines - Slobodan Dmitrovic
    MISRA C++ 2023 - Richard Kaiser

 

Trip Report: CppCon 2025 -- Sandor Dargo

By Blog Staff | Oct 14, 2025 01:10 PM | Tags: None

A long-delayed dream finally came true: after years of near-misses and lessons learned (“better to be invited than sent”), I made it to CppCon—and it was bigger, louder, and more inspiring than I imagined. In this recap I share the vibe of the week, five standout talks and ideas, a few notes from my own session, and links to recordings as they appear.

Trip Report: CppCon 2025

by Sandor Dargo

From the article:

CppCon is simply bigger than any other C++ conference I’ve attended. A massive venue packed with people and sponsors. I logged more than 10,000 steps on the very first day — without ever leaving the resort or going to the gym.

The whole experience felt like it was on another scale compared to European conferences (which I also love). But then again, that’s often the impression when you see something American from a European perspective, isn’t it?

I never would have imagined a C++ conference where a live band plays while Bjarne Stroustrup himself makes final checks before stepping on stage to deliver the opening keynote. Absolutely rocks.

Rainer Grimm passed last week

By Meeting C++ | Oct 14, 2025 07:24 AM | Tags: community

Sadly I have to inform you about Rainer Grimms passing last week. He was a great C++ author, trainer, speaker and friend. Heartfelt condolences to his family.

Rainer Grimms ALS Journey 31/31: the end

by Beatrix Grimm

From the article:

Dear readers, we are extremely sad to inform you that Rainer passed away on October 6, 2025, surrounded by his closest family. After suffering from life-threatening pneumonia, Rainer decided against further life-sustaining measures that would have severely restricted his life. He passed away peacefully, accompanied by his family.

Structured Bindings in C++17, 8 Years Later -- Bartlomiej Filipek

By Blog Staff | Oct 9, 2025 12:42 PM | Tags: None

Structured binding is a C++17 feature that allows you to bind multiple variables to the elements of a structured object, such as a tuple or struct. This can make your code more concise and easier to read, especially when working with complex data structures. On this blog, we already covered this functionality, but we’ll talk about some good C++26 additions and real code use cases.

Structured bindings in C++17, 8 years later

by Bartlomiej Filipek

From the article:

An excellent demonstration of structured bindings is an iteration through a map object.

If you have a std::map of elements, you might know that internally, they are stored as pairs of <const Key, ValueType>.

Now, when you iterate through elements, you can do:

for (const auto& elem : myMap) { ... } 

You need to write elem.first and elem.second to refer to the key and the value.

std::map<KeyType, ValueType> myMap = getMap(); 
// C++14: 
for (const auto& elem : myMap) {  
     // elem.first - is the key  
     // elem.second - is the value 
}

You should use QPainterPath they said...

By Meeting C++ | Oct 8, 2025 10:21 AM | Tags: qt meetingcpp community

A blog entry about this years t-shirt at Meeting C++ 2025 and exploring QPainterPath for it.

You should use QPainterPath they said...

by Jens Weller

From the article:

This post is about what I learned while playing around with QPainterPath for this years t-shirt at Meeting C++ 2025 sponsored by Hudson River Trading.

One of the issues from last years t-shirt was when using drawText from QPainter, one does not really *draw* text in an svg exported. Instead you'll get the text and the font kinda embedded in an svg. What good is that in a vector graphic? This was a bit of a surprise when I ran into issues with this last year during printing. While this could be solved with the printing company picking a different font, it would have been also solved by using QPainterPath. At least this was the feedback from some of the Qt experts present onsite or online...

 

Final call for sponsors for Meeting C++ 2025

By Meeting C++ | Oct 6, 2025 01:04 PM | Tags: meetingcpp conference community

With Meeting C++ 2025 coming closer, we're doing a last round of onboarding for sponsors

Final call for sponsors for Meeting C++ 2025

by Jens Weller

From the article:

With Meeting C++ 2025 just being 5 weeks away, I share a call for sponsors with you.

Maybe your employer is interested in being present as a sponsor at this years Meeting C++ conference? Have you thought about the possibilty that you could have your employer sponsor Meeting C++ 2025?

As an organization Meeting C++ gets its funding through sponsorship and ticket sales for the conference mostly.

How to Look up Values in a Map -- Sandor Dargo

By Blog Staff | Oct 1, 2025 12:38 PM | Tags: None

Whether you’re in a coding interview or writing production code, you’ll eventually face the question: What’s the right way to look up values in a std::map or std::unordered_map? For simplicity, we’ll refer to both containers as maps in this post.

How to Look up Values in a Map

by Sandor Dargo

From the article:

Let’s explore the different options — along with their pros and cons.

operator[]

Using operator[] is the old-fashioned way to access elements of a map. It takes a key and returns a reference to the corresponding value. The complexity is log(n) for std::map and average constant time (with worst-case linear) for std::unordered_map.

However, there’s a big caveat.

What if the key is not present in the map?

Unlike a vector — where accessing an invalid index with operator[] leads to undefined behavior — a map will instead insert a new entry with the given key and a default-constructed value. This side effect makes operator[] unsafe for lookups where insertion is not desired.

Safely passing strings and string_views -- Niek J Bouman

By niekb | Sep 27, 2025 02:00 PM | Tags: None

Passing a string temporary into a string_view can make the latter dangling 

Safely passing std::strings and std::string_view

by Niek J Bouman

From the article:

Many of you will agree that C++ is a language that comes with sharp edges. One example is `std::string_view`; introduced as a type to prevent unnecessary std::string-copies, but it introduces a new footgun, namely when passing a temporary string into it:

A safer C++ pointer class -- Niek J. Bouman

By niekb | Sep 27, 2025 01:58 PM | Tags: None

Sometimes some object A needs to interact with another object B, e.g., A calls one of B’s methods. In a language like C++, it is left to the programmer to assure that B outlives A; if B happens to be already destructed, this would be a use-after-free bug. Managing object lifetimes can be tricky, especially with asynchronous code.

A safe pointer in C++ that protects against use after free and updates when the pointee is moved

by Niek J. Bouman

From the article:

We propose a design for a safe pointer to an object of type T that is weak in that it does not have ownership semantics, and gets notified in case the pointee is either destructed or moved.

We will pay a price at runtime for these extra guarantees in terms of a small heap-allocated state, a double pointer indirection when accessing the pointee (comparable to a virtual function call), and a check against nullptr.

The main idea of our design is to internally use a std::shared_ptr<T*> to share ownership of a (heap-allocated) pointer T*. The ownership is shared by the pointee and all safe_ptr<T> instances. The pointee type T must derive from the base class safe_ptr_factory (templated on T, using the Curiously Recurring Template Pattern) with a destructor that automatically notifies the shared state about destruction by setting T* to nullptr, and with a move constructor and move assignment operator that update T* to the new this pointer (which we must properly cast with static_cast<T*>). The double indirection thus comes from having to dereference the shared_ptr to obtain an ordinary pointer T*, after which you must dereference once more to access the pointee. You might recognize an instance of Gang-of-Four’s observer pattern in our design.

Linus Torvalds and the Supposedly Garbage Code -- Giovanni Dicanio

By Giovanni Dicanio | Sep 27, 2025 01:53 PM | Tags: None

Some reflections on a harsh critic by Linus Torvalds on a RISC-V Linux kernel contribution. 

Linus Torvalds and the Supposedly “Garbage Code”

by Giovanni Dicanio

From the article:

So, the correct explicit code is not something as simple as “(a << 16) + b”.

[...] As you can see, the type casts, the parentheses, the potential bit-masking, do require attention. But once you get the code right, you can safely and conveniently reuse it every time you need!