-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
27e9352
commit fb0fc07
Showing
1 changed file
with
41 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
--- | ||
layout: post | ||
nav-class: dark | ||
categories: company, vinnie | ||
title: Safe C++ Partnership | ||
author-id: vinnie | ||
--- | ||
|
||
# Safe C++ Partnership | ||
|
||
I am happy to announce that the C++ Alliance has formed a partnership with | ||
Sean Baxter, a renowned engineer, to develop the Safe C++ Extensions. | ||
This is a revolutionary proposal that adds memory safety features to the C++ | ||
programming language. | ||
|
||
This collaboration marks a significant milestone in the C++ ecosystem, as the | ||
need for safe code has never been more pressing. With the increasing importance | ||
of software security and reliability, developers are facing mounting pressure to | ||
adopt safer coding practices. The Safe C++ Extensions aim to address this | ||
critical need by introducing novel features that prevent common memory-related | ||
errors. | ||
|
||
We are thrilled to be working with Sean Baxter on this crucial initiative. | ||
The Safe C++ Extensions represent a major step forward in making C++ more secure | ||
and efficient, while preserving the language's performance and flexibility. | ||
|
||
The Safe Standard Library is a key component of the Safe C++ Extensions proposal. | ||
This extensive library addition will provide developers with robust, memory-safe | ||
implementations of essential data structures and algorithms. By integrating these | ||
components into the C++ Standard Library, we can ensure that new code is written | ||
with safety in mind from the outset. | ||
|
||
The C++ Alliance and Sean Baxter are seeking feedback from developers, researchers, | ||
and other stakeholders on the Safe C++ Extensions proposal. This collaborative | ||
process will help refine the project's scope and ensure that it addresses the most | ||
pressing needs of the C++ ecosystem. | ||
|
||
To view the latest draft of the Safe C++ Extensions proposal, learn more about | ||
Safe C++, or participate in discussions, please visit the official website at | ||
https://safecpp.org or join us in the Official C++ Language Slack Workspace | ||
by signing up at https://cpp.al/slack and visiting the #safe-cpp channel. |