Testing Algorithm lib

That’s a wrap on Pure Virtual C++ 2026! Thank you to everyone who joined us live, asked questions in the chat, and made this year’s free, one-day C++ conference such a great time. Huge thanks to our hosts Mads Kristensen and Sinem Akinci, to every speaker who shared their work, and to the moderators who kept the conversation going.

Missed a session, or want to rewatch? All talks, both the live broadcast featured sessions and the on-demand sessions, are available now.

Watch the full playlist on YouTube →


Featured sessions

These were introduced live during the broadcast, in this order:

Next Post

  • No Tag- Backwards Compatibility
    Blog
    Backwards compatibility in Boost libraries is addressed through a set of guidelines that classify changes by their impact. Non‑breaking modifications may be introduced without restriction. Small breaking changes are permitted provided advance notice is given several releases before publication. Large breaking changes that include a migration path require the new API to be placed in a separate directory or namespace, with users notified and afforded several releases to transition before the old API is removed. When no migration path exists, the new API must also reside in a distinct directory or namespace, while the legacy API is retained indefinitely, and removal is treated as a library deprecation requiring an extended period. Redesigns or rewrites equivalent to large breaking changes are to be considered new libraries and should undergo a formal or mini review.