Structured Bindings demystified

on YouTube ↗10m

" summary

Explains that structured bindings declare identifiers for subobjects not for the whole object, so the bound names refer to members and not a named temporary. Shows the surprising ABI/semantics consequence: structured bindings disable RVO for the bound subobject so a copy can occur where a plain auto pair would let RVO apply. Demonstrates the tuple protocol (tuple_size / tuple_element / get) and a practical pattern: a single templated friend get using forwarding references and decay that generates the needed reference categories and works for lvalue/rvalue/const cases.

AI-written summary · about

" chapters (6)

1. 0:00Introduction
2. 0:18Use cases
3. 3:27Paper
4. 3:53Solution
5. 5:24Tuple Protocol
6. 7:04Get

" related talks

• 12mGeneric BindingChristoph Wanzke · Meeting C++ 2015
• 01h 07mBack to Basics: Templates (part 2 of 2)Bob Steagall · CppCon 2021
• 05mWishful ThinkingRoland Bock · CppCon 2014
• 52mBuilding Bridges: C++ Interop, Foreign Function Interfaces & ABIGareth Williamson · Meeting C++ 2025
• 36mThe language that isn'tEsteban Kuber · RustFest LATAM 2022
• 05mF.21Guiseppe D'Angelo · CppCon 2017
• 01h 01mBreaking Dependencies - C++ Type Erasure - The Implementation DetailsKlaus Iglberger · CppCon 2022
• 28m"Rust Interop: Memory Safety Across Foreign Function Boundaries"Joannah Nanjekye · RustConf 2024