Arno Schödl
Why Iterators Got It All Wrong — and what we should use instead
#1about 1 minute
The dual role of C++ iterators as elements and borders
C++ iterators, modeled after pointers, are used ambiguously to represent both specific elements and the borders between them.
#2about 1 minute
Writing cleaner code with C++ ranges
C++20 ranges simplify code by reducing the boilerplate of begin() and end() calls required with traditional iterator pairs.
#3about 4 minutes
Using range adapters for lazy transformations
Range adapters like transform allow for lazy evaluation, separating data projection from the search operation for more modular code.
#4about 2 minutes
How filter adapters create ambiguity for borders
The filter adapter demonstrates a flaw where mapping a border from a filtered range back to the original range is ambiguous.
#5about 5 minutes
The core problem with the reverse adapter
The reverse adapter proves that a single .base() method cannot correctly map both elements and borders back to the original range.
#6about 3 minutes
A formal solution with element and border concepts
The fundamental iterator flaw can be solved by introducing two distinct concepts: 'border' for positions between items and 'element' for the items themselves.
#7about 4 minutes
Improving algorithms with nullable elements and better names
Further improvements include making element types nullable to handle 'not found' cases cleanly and using more descriptive algorithm names like binary_find.
#8about 2 minutes
Conclusion and the think-cell range library
The think-cell C++ range library implements concepts like nullable elements and refined algorithms to address the inherent flaws in standard iterators.
#9about 4 minutes
Q&A on iterator invalidation and border types
The speaker addresses audience questions regarding how the border and element distinction interacts with container iterator invalidation and mathematical open or closed intervals.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
20:55 MIN
Processing large datasets with the iterator pattern and streams
10 must-know design patterns for JS Devs
00:15 MIN
Debunking common myths about C++ in constrained systems
C++ in constrained environments
14:38 MIN
Using modern language features for safer code
C++ in constrained environments
06:40 MIN
Modern C++ evolution and the burden of backward compatibility
Eternal Sunshine of the Spotless Programming Language
00:36 MIN
Understanding the original design goals and evolution of C++
Eternal Sunshine of the Spotless Programming Language
21:38 MIN
Using design to create workarounds for bad data
Design as an algorithm, not as a feature
52:52 MIN
Q&A on local error handling and C++23 features
C++ in constrained environments
05:06 MIN
Analyzing different developer approaches to coding challenges
Dev Digest End of Year Recap
Featured Partners
Related Videos
The C++ rvalue lifetime disaster
Arno Schoedl
C++ Features You Might Not Know
Jonathan Müller
C++ in constrained environments
Bjarne Stroustrup
101 brilliant things of C++
Andreas Fertig
Functional Programming in C++
Jonathan Müller
The Design and Evolution of C++
Bjarne Stroustrup
An (In-)Complete Guide to C++ Object Lifetimes
Jonathan Müller
Eternal Sunshine of the Spotless Programming Language
Stefan Baumgartner
From learning to earning
Jobs that call for the skills explored in this talk.





C++ Entwickler Video / Grafik | C++ 17 / 20, OpenGL, Vulkan, codec, multithreading | Inhouse (mwd)
Vesterling Consulting GmbH
Remote
€55-80K
API
C++
Bash
+7




Softwareentwickler_in C/C++ | Embedded Robotic
Servus Intralogistics Gmbh
€53K
C++
Software Architecture
Test Driven Development