No, this is not an "ABI - Now or Never" talk. What happens in Prague, stays in Prague :) But wg21.link/P1863 will probably come up in the discussions, so we might as well prepare for it.
We're taking a different route, by following the design and evolution of the Swift ABI model and seeing what we can learn from it. From ABI stability & dynamic linking to designing for ABI resilience - a journey through resilient type layout, reabstraction & materialization, resilience in library evolution and (opt-out) performance costs.
What can we learn from Swift's ABI resilience? Can C++ be liberated from the ABI conundrum?