A program built for people who read release notes for fun.
20 sessions · Day 01
8:30 am
Registration & Morning Coffee
9:00 am
Keynote
Opening Remarks
Dr. Leah Ramirez
plenary
9:20 am
Keynote
Beyond the Standard: Modern C++ Directions for the Next Decade
Prof. Bernard Okafor
plenary
10:05 am
Short Break
10:15 am
Talk
Core Language
Toward Zero-Overhead Reflection: A Compile-Time Introspection Framework
Dr. Jason Lee
10:15 am
Talk
Performance
Shipping C++20 Modules in Legacy Codebases: A Postmortem After 18 Months in Production
Samantha Patel
10:15 am
Talk
Tooling
Dark Patterns in Package Managers: Who Audits vcpkg Dependencies?
Malik Mensah
10:50 am
Talk
Core Language
Memory Model Pitfalls: Quantifying the Cost of “Relaxed” Atomics
Dr. Silvia Rossi
10:50 am
Talk
Performance
Continuous Benchmarking You Can Trust: Building a Performance Baseline for 100M LOC
Jonathan Kim
10:50 am
Talk
Tooling
Green Builds: Carbon-Aware Compilation Strategies for Large C++ Projects
Dr. Emma Park
11:25 am
Lightning
Core Language
Lightning Talks - Core Language Track
11:25 am
Lightning
Performance
Lightning Talks - Performance Track
11:25 am
Lightning
Tooling
Lightning Talks - Tooling Track
12:00 pm
Lunch
1:15 pm
Keynote
Beyond O(1): Algorithmic Design Patterns for Real-Time Systems in C++
Angela Rivera
plenary
2:00 pm
Talk
Core Language
The Cost of std::vector Growth: Quantitative Analysis in Hot Loops
Dr. Marcus Evans
2:00 pm
Talk
Performance
Latency Spikes and Text Logging: Lessons from 10k TPS Trading Systems
Lauren Schneider
2:00 pm
Talk
Tooling
Right to Repair Meets Firmware: Legal Views on Locked-Down Toolchains
Dr. Aisha Rahman
2:35 pm
Talk
Core Language
Exascale Parallelism with std::execution: Early Results from Aurora
Noah Bekele
2:35 pm
Talk
Performance
No-Footgun Smart Pointers: A Practitioner’s Honest Assessment
Viktor Petrov
2:35 pm
Talk
Tooling
Bias in Branch Predictors: Security Implications for C++ JITs
Dr. Heidi Sørensen
3:10 pm
Afternoon Break
3:35 pm
Panel
Is the UB-Fear Overstated? Measuring Real-World Impact on Safety-Critical Code
plenary
4:35 pm
Keynote
Day One Close & Community Announcements
Dr. Brian Choi
plenary
5:00 pm
Evening Reception - Foyer & Rooftop Terrace
Why C++ Fall 26
Built for C++ people.
Zero-cost abstractions
Talks that respect performance reality
No hand-wavy futurism. Expect code, benchmarks, trade-offs, build pain, and the kinds of details only practitioners bother to argue about.
Tooling renaissance
Compilers, build systems, static analysis, and debuggers
From clang internals to editor workflows to modern CI and package management, this is where the people doing the hard work compare notes.
Language evolution
Where modern C++ is actually going
Executors, reflection, safety, modules, ergonomics, performance portability — ideas discussed by people who understand both the standard and the field.
Systems people
A crowd worth meeting
Library authors, engine programmers, compiler engineers, infra leads, finance, embedded, graphics, robotics — exactly the kind of unfiltered C++ conversations you hope for.
What people say
The kind of praise that sounds like a code review compliment.
“
Finally, a C++ event where the talks assumed the audience had a profiler and knew how to use it.
MK
Mina Kovács
Compiler Engineer
“
Dense, technical, opinionated, and weirdly elegant. Exactly what a good C++ conference should be.
DM
Daniel Mercer
Game Engine Programmer
“
The between-talks C++ conversations alone were worth. I left with ideas for tooling, hiring, and a library redesign.
PS
Priyanka Sethi
Staff Systems Engineer
Call for speakers
Have a sharp idea, a hard-earned lesson, or a benchmark with a story behind it?
patch welcome
Submit a proposal.
Great talks can be deeply practical, surprisingly opinionated, narrowly technical, or elegantly conceptual — as long as they are grounded in real engineering.
diff --git a/idea.md b/stage.md
index old..new 100644
+ Title: What We Learned Rewriting a Critical Path in Modern C++
+ Format: Talk / Panel / Workshop
+ Audience: Engineers who care about correctness and speed
+ Show us:
+ - the constraints
+ - the trade-offs
+ - the tooling
+ - the measurements
+ - the part that went wrong
+ Bonus points for:
+ - benchmarks with context
+ - codebase scale
+ - surprising conclusions
+ - brutal honesty
