2025-09-28 –, Auditorium B001 (170)
In continuation from my talk on quantifying abstractions by objective costs, we also need to evaluate the more subjective costs and benefits of this work, as well as where that work should be directed. Ideally this will form the basis of a design document that developers can refer to for guidance, further reducing friction between developers and maintainers by making expectations more clear.
We will talk about and evaluate:
- acceptability and like/dislike of different abstractions and practices
- what is most important to refactor/rewrite/modernize, and the risks of doing so
- refresh our state on goals, ImprovementProjects, and rearch plans (some of this is very old)
- figure out what changes we really want
- and very importantly, what we do NOT want our code base to become
To help stimulate discussion, I will prepare examples of code with potential refactors (some intentionally bad).
This builds on top of my previous talk "Quantifying Abstraction Costs in GCC", if you plan on attending this BOF it would be beneficial to attend that talk to develop more background.
Compiler Engineer/Code Sourcerer at BayLibre
Contributor of GCC's implementation of C++ P0847R7 Deducing this
Member of The ISO C++ committee (ISO/IEC JTC1 / SC22 / WG21)
Co-Author of P3668 Defaulting Postfix Increment and Decrement Operations