Loading...

Tag trends are in beta. Feedback? Thoughts? Email me at matthew@mastracci.com

TrapC: Memory Safe C Programming with No UB

Note to the C++ standards committee members on profiles and safety

F-strings for C++26 proposal [pdf]

Standard proposal for memory-Safety in C (2024)

An effect system proposal for C2y

Stroustroup: We need better performance testing [pdf]

(Re)affirm design principles for future C++ evolution

Memory safety without lifetime parameters

C++ proposal: There are exactly 8 bits in a byte

Locales, Encodings, and Unicode

The C Standard charter was updated, now with security principles as well

P3292R0R0: Provenance and Concurrency

A proposal for the next version of C [pdf]

Polymorphic Types in C [pdf]

C++ Should Be C++

Improving our safety with a physical quantities and units library

Implication for C++ [pdf]

What is ABI and what should WG21 do about it? (2020)

UB? In My Lexer? [pdf]

C++ is the next C++

Bjarne Stroustrup: Think seriously about “safety”...

DG Opinion on Safety for ISO C++

C++ Is the Next C++

Design Alternatives for Type-and-Resource Safe C++: Bjarne Stroustrup and Gabriel Dos Reis

The initial proposal for a C++ Ecosystem International Standard

Guide for the use of the Ada Ravenscar Profile in high integrity systems

C23 working draft (7/6/22)

C++ exceptions are becoming more and more problematic

A simple defer feature for C

P2000r3: Direction for C++

More →