<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/becpp-symposium-2026---andre-kostur---there-s-a-hole-in-the-c-type-system-ptcpzzvur" -->

---
title: BeCPP Symposium 2026 - Andre Kostur - There’s a Hole in...
description: A C++ committee member describes discovering a gap in operator arrow (operator->) semantics that allows reference-qualified member functions (rvalue-deleted...
canonical: https://daily.dev/posts/becpp-symposium-2026---andre-kostur---there-s-a-hole-in-the-c-type-system-ptcpzzvur
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: BeCPP Symposium 2026 - Andre Kostur - There’s a Hole in the C++ Type System | daily.dev
og:description: A C++ committee member describes discovering a gap in operator arrow (operator->) semantics that allows reference-qualified member functions (rvalue-deleted...
og:url: https://daily.dev/posts/becpp-symposium-2026---andre-kostur---there-s-a-hole-in-the-c-type-system-ptcpzzvur
og:image: https://api.daily.dev/og/posts/PtcPzZvUR.png
og:image:alt: BeCPP Symposium 2026 - Andre Kostur - There’s a Hole in the C++ Type System
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# BeCPP Symposium 2026 - Andre Kostur - There’s a Hole in the C++ Type System

**[C\+\+](https://daily.dev/sources/isocpp)** · 39 min read · 1 upvotes · 0 comments

## Summary

A C++ committee member describes discovering a gap in operator arrow (operator->) semantics that allows reference-qualified member functions (rvalue-deleted overloads) to be silently bypassed when chained through operator arrow, because arrow chains always collapse to a raw pointer, losing value category information that operator star (operator*) preserves. The talk walks through how the bug was found via a code review involving a company-internal IDL generating C++ with std::optional, why it causes dangling iterator undefined behavior, the mitigation via a custom clang-tidy check, and the process of turning the fix into a standards proposal (adopting and extending paper P3039, aiming for operator-> to default to operator* when undeclared). It also details engaging with the WG21 committee, mailing lists, straw polls at the Kona and recent ISO meetings, unresolved questions around std::to_address and pointer_traits specialization, and the multi-year path (targeting C++29) required to land a language change.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://youtu.be/gM-Vus6oJ98>

## Questions this post answers

### Why does calling operator-> on a temporary std::optional bypass a reference-qualified deleted member function in C++?

Operator-> always resolves down to a raw pointer per the C++ standard's expression-rewriting rules, and dereferencing that pointer via the compiler-inserted rewrite yields an lvalue, not an rvalue reference. This means an rvalue-qualified (deleted) overload, intended to block use on temporaries, gets silently skipped in favor of the lvalue overload, unlike calling .value() or operator* directly, which are reference-qualified and correctly produce an rvalue reference.

_Anyone chasing dangling-iterator bugs from temporary optionals can track this operator-> proposal's progress on daily.dev._

### What is C++ proposal P3039 and how does it relate to fixing the operator-> reference qualification problem?

P3039, originally written in November 2023, proposes letting a class automatically fall back from operator-> to operator* when no operator-> is declared, so smart-pointer-like classes need not write both. Because operator* can be reference-qualified, this fallback would let overload resolution correctly distinguish rvalue from lvalue temporaries, fixing the dangling-iterator hazard while leaving existing code with an explicit operator-> unaffected.

_Developers weighing future smart-pointer designs can follow this proposal's evolution through daily.dev before it reaches C++29._

### How does a C++ language change proposal move through the WG21 standardization process to reach the standard?

A proposal goes through mailing-list feedback, then revisions presented to Library Evolution (LEWG) and Evolution (EWG) working groups at in-person ISO meetings, gathering straw polls and consensus (not simple majority). Once evolution groups approve, Core Working Group handles formal wording, then plenary votes move it into the working draft, later the draft international standard, and finally national body votes ratify it as the published standard, typically taking years across multiple meeting cycles.

_Engineers curious how a proposal like this reaches a future C++ standard can follow its meeting-by-meeting progress on daily.dev._

## Similar posts on daily.dev

- [C\+\+26: Reducing undefined behaviour](https://daily.dev/posts/c-26-reducing-undefined-behaviour-tbbsne1hb) · Sandor Dargo · 0 upvotes · 0 comments
- [The C\+\+ fundamentals your seniors think they know](https://daily.dev/posts/the-c-fundamentals-your-seniors-think-they-know-lgmt2lsp3) · C\+\+ · 0 upvotes · 1 comments
- [Why does the arrow \(->\) operator in C exist?](https://daily.dev/posts/why-does-the-arrow---operator-in-c-exist--yx4ophdjx) · Lobsters · 1 upvotes · 0 comments
- [How my papers did at Kona](https://daily.dev/posts/how-my-papers-did-at-kona-eibyurnad) · Arthur O'Dwyer · 1 upvotes · 0 comments

---

Tags: [#c++](https://daily.dev/tags/c++)

[View this post on daily.dev](https://daily.dev/posts/becpp-symposium-2026---andre-kostur---there-s-a-hole-in-the-c-type-system-ptcpzzvur)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"BeCPP Symposium 2026 - Andre Kostur - There’s a Hole in the C++ Type System","url":"https://daily.dev/posts/becpp-symposium-2026---andre-kostur---there-s-a-hole-in-the-c-type-system-ptcpzzvur","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/becpp-symposium-2026---andre-kostur---there-s-a-hole-in-the-c-type-system-ptcpzzvur"},"datePublished":"2026-08-28T06:36:42.936Z","dateModified":"2026-09-13T20:35:51.177Z","description":"A C++ committee member describes discovering a gap in operator arrow (operator-\u003e) semantics that allows reference-qualified member functions (rvalue-deleted...","image":"https://i.ytimg.com/vi/gM-Vus6oJ98/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/gM-Vus6oJ98/sddefault.jpg","isAccessibleForFree":true,"articleSection":"C++","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"C++","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/c96d1356acb34a8d982064453dcfeb20","url":"https://daily.dev/sources/isocpp"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/becpp-symposium-2026---andre-kostur---there-s-a-hole-in-the-c-type-system-ptcpzzvur","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"c++","timeRequired":"PT39M","video":{"@type":"VideoObject","name":"BeCPP Symposium 2026 - Andre Kostur - There’s a Hole in the C++ Type System","description":"A C++ committee member describes discovering a gap in operator arrow (operator-\u003e) semantics that allows reference-qualified member functions (rvalue-deleted...","thumbnailUrl":"https://i.ytimg.com/vi/gM-Vus6oJ98/sddefault.jpg","uploadDate":"2026-08-28T06:36:42.936Z","duration":"PT39M","url":"https://api.daily.dev/r/PtcPzZvUR","embedUrl":"https://www.youtube.com/embed/gM-Vus6oJ98"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"C++","item":"https://daily.dev/sources/isocpp"},{"@type":"ListItem","position":3,"name":"BeCPP Symposium 2026 - Andre Kostur - There’s a Hole in the C++ Type System"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/becpp-symposium-2026---andre-kostur---there-s-a-hole-in-the-c-type-system-ptcpzzvur#faq","mainEntity":[{"@type":"Question","name":"Why does calling operator-\u003e on a temporary std::optional bypass a reference-qualified deleted member function in C++?","acceptedAnswer":{"@type":"Answer","text":"Operator-\u003e always resolves down to a raw pointer per the C++ standard's expression-rewriting rules, and dereferencing that pointer via the compiler-inserted rewrite yields an lvalue, not an rvalue reference. This means an rvalue-qualified (deleted) overload, intended to block use on temporaries, gets silently skipped in favor of the lvalue overload, unlike calling .value() or operator* directly, which are reference-qualified and correctly produce an rvalue reference. Anyone chasing dangling-iterator bugs from temporary optionals can track this operator-\u003e proposal's progress on daily.dev."}},{"@type":"Question","name":"What is C++ proposal P3039 and how does it relate to fixing the operator-\u003e reference qualification problem?","acceptedAnswer":{"@type":"Answer","text":"P3039, originally written in November 2023, proposes letting a class automatically fall back from operator-\u003e to operator* when no operator-\u003e is declared, so smart-pointer-like classes need not write both. Because operator* can be reference-qualified, this fallback would let overload resolution correctly distinguish rvalue from lvalue temporaries, fixing the dangling-iterator hazard while leaving existing code with an explicit operator-\u003e unaffected. Developers weighing future smart-pointer designs can follow this proposal's evolution through daily.dev before it reaches C++29."}},{"@type":"Question","name":"How does a C++ language change proposal move through the WG21 standardization process to reach the standard?","acceptedAnswer":{"@type":"Answer","text":"A proposal goes through mailing-list feedback, then revisions presented to Library Evolution (LEWG) and Evolution (EWG) working groups at in-person ISO meetings, gathering straw polls and consensus (not simple majority). Once evolution groups approve, Core Working Group handles formal wording, then plenary votes move it into the working draft, later the draft international standard, and finally national body votes ratify it as the published standard, typically taking years across multiple meeting cycles. Engineers curious how a proposal like this reaches a future C++ standard can follow its meeting-by-meeting progress on daily.dev."}}]}
```

