John_C++ “安全优先”开发模式演进与路线图.pdf

《John_C++ “安全优先”开发模式演进与路线图.pdf》由会员分享，可在线阅读，更多相关《John_C++ “安全优先”开发模式演进与路线图.pdf（78页珍藏版）》请在三个皮匠报告上搜索。

1、 2025 Bloomberg Finance L.P.All rights reserved.What C+Needs to be Safe?C+C+需要些什么才能安全？需要些什么才能安全？C+Summit25December 12-13,2025Modified Monday,Dec 1st,2025John LakosSenior Architect,Office of the CTO 首席技术官办公室高级架构师What C+Needs to be Safe?John LakosBloomberg,CTORevised December 1,20257AbstractThe world

2、runs on C+.For more than two decades,C+has served as the workhorse of high-performance,low-power,and low-latency software across industries.Its raw speed and unconstrained flexibility have made C+the go-to language for and backbone of large-scale software development.C+是驱动世界运转的核心语言。二十多年来，它始终是各行业高性能、

3、低功耗、低延迟软件的主力担当。凭借其极致速度与无拘无束的灵活性，C+已成为大规模软件开发的首选语言和核心支柱。Recently,however,software engineering priorities have shifted significantly toward safety.While C+enables the creation of secure and correct programs,its traditional focus has favored performance over safety guarantees.As the software landscape

4、evolves,C+faces a crucial inflection point.To maintain its unparalleled stature,C+must embrace various safety mechanisms along with safety-by-default principles to support a broader developer ecosystem while preserving the performance capabilities that experts will continue to demand.然而近年来，软件工程的重心已显

5、著向安全性倾斜。尽管 C+语言能够开发出安全可靠的程序，但其传统定位始终更侧重性能而非安全保障。随着软件生态的持续演进，C+正面临关键转折点。为保持其无可替代的地位，C+必须拥抱多种安全机制与默认安全原则，既要维护开发者生态系统的广泛性，又要确保满足技术专家持续追求的性能表现。This talk will examine C+s evolution toward safety-first development,analyzing functional,language,memory,lifetime,and data-race safety considerations.We survey

6、existing safety techniques,identify current limitations,and explore potential solutions for remaining security challenges.Finally,we present a comprehensive roadmap for achieving robust safety guarantees in C+26 and beyond,while continuing to enable all the languages performance advantages.本次演讲将深入探讨