An Update on Writing Memory Safety Bugs

How could we write better software, and write software better?

---

A blog by danakj Email GitHub Mastodon RSS

I am computer scientist and software security engineer at Chromium, with an strong interest in programming languages, APIs, developer education, security and memory safety. While I am excited about Rust, there is a lot of C++ in this world. Security-crtical C++ projects have a history of being a risk to their users, so I want to improve how we write C++.

This blog is largely documenting my C++ language research and experience building the Subspace library and associated tooling.

See the archive for a list of all posts.

• How to Build Abstractions in Rust Applications: The Missing Rung on the Rust Education Ladder

• Integer overflow and arithmetic safety in C++

• Complexity of reference containers

• On push_back_unchecked: Performance with FromIterator and Collect

• A tale of C/C++ development in three parts

• Comparing floats in Subspace and stdlib

• Implementing Iterator::flatten() in C++ and in Rust

• Bounds Safety: Avoiding Death by a Thousand Constructors

• Subspace Update: Slices and Vec, Generators, More Iterators, Std Ranges, Callable concepts

• Me versus C++ Mutable References.

• Trivially Relocatable Types in C++/Subspace

• Why Subspace

• Designing a Tagged Union type in C++/Subspace