An update on TrapC progress

Baltimore, MD (trapc.org) 26 January 2026 – About a year ago in February of 2025, I presented a whitepaper to the ISO C Committee meeting TrapC: Memory Safe C Programming with No UB. The White House had released its Building Blocks report in February 2024, calling for replacing C/C++ with memory safe languages such as Rust or Python. That generated some pushback from the C++ community, but there was no solid plan what to do about the treachery of C/C++ pointers and the crashes and exploits that result from pointer misuse.

It’s not as though nobody had tried to fix C and C++ memory issues. Memory safety had been a concern from the beginning of the C programming language back in the 1970s. However, despite many attempts over decades, nobody had found an elegant and efficient answer to the C/C++ memory safety problem.

In March 2024, as a member of the ISO C++ Committee, I attended the committee meeting in Tokyo, with 200 others gathering to define the C++26 standard. I had earlier presented TrapC as a concept, but many questions remained how to define TrapC implementation. That was my mindset in Tokyo, that I had a workable concept for memory safety, not all the implementation details necessary to build it. In Tokyo, the talk was about reflection templates and other C++26 proposals, not so much memory safety.

...read more at trapc.org