Tag
Describes Fil-C's InvisiCaps capability model for ensuring memory safety in C and C++ by tracking pointer permissions, while aiming for fanatical compatibility and reasonable performance.
This paper presents a modified Rust compiler for the Morello capability hardware architecture, enabling always-on memory safety even in unsafe code by leveraging hardware capabilities.
This article discusses a fundamental memory safety challenge involving tagged unions where a pointer to one variant is used after the union is overwritten with a different variant, leading to type confusion. The author also argues that buffer overflows are the most exploitable memory error and could have been mitigated with better array syntax.
A critique of null-terminated strings in C, arguing that length-based strings are superior for modern programming, leading to fewer bugs and better performance.
Jarred Sumner details the agentic rewriting of Bun from Zig to Rust using AI, costing $165k in tokens and resulting in a 10% faster startup.
Fil-C introduces memory-safe implementation of setjmp/longjmp and ucontext APIs, preventing dangling stack corruption and panicking on misuse.
OpenAI engineers detail the diagnosis of seemingly impossible crashes in Rockset's C++ data infrastructure, revealing both a silent hardware corruption bug on Azure and an 18-year-old race condition in GNU libunwind, resolved through epidemiological analysis of crash data.
Explains the `std::pin::Pin` type in Rust, why pinning is needed for self-referential types like async state machines, and how `Pin` prevents moves while allowing safe mutation.
Ante introduces a novel approach to blending borrow checking and reference counting without runtime crashes, enabling developers to use both paradigms seamlessly in a systems programming language.
Apple has begun integrating Swift into the kernel via a new effort called KernelKit, with an Embedded Swift runtime appearing in macOS and iOS, marking a step toward memory-safe kernel extensions.
Fil-C introduces memory-safe inline assembly, ensuring that programmer errors result in panics or traps rather than miscompilation.
cuTile Rust introduces a tile-based programming model that leverages Rust's ownership to guarantee memory safety and data-race freedom for GPU kernels, and the Grout inference engine built on it achieves competitive throughput with vLLM/SGLang for Qwen3 models.
NVIDIA Labs releases cuTile Rust, a tile-based system for writing memory-safe, data-race-free GPU kernels in idiomatic Rust. It extends Rust's ownership model to GPU kernels, JIT-compiles Rust AST to GPU code, and achieves performance close to native CUDA.
An analysis of how memory safety CVEs are reported differently in Rust vs C/C++, arguing that Rust's design reduces certain classes of vulnerabilities even when bugs exist.
Apple migrated the TrueType hinting interpreter from C to Swift, achieving memory safety and a 13% performance improvement. The source code has been open-sourced.
Fil-C 0.679 is a new release of a fanatically compatible memory-safe implementation of C and C++ that uses concurrent garbage collection and invisible capabilities to prevent all memory safety errors without escape hatches.
This article introduces a new approach to memory safety based on linear types and abstract interpretation, aiming to eliminate common bugs like use-after-free and memory leaks more ergonomically than Rust.
Anthropic acquired Bun and used Claude Code agents to rewrite the entire runtime from Zig to Rust in nine days. The rewrite passed 99.8% of tests but introduced over 10,000 unsafe blocks, raising questions about the benefits of memory safety.
This article introduces iddqd, a Rust library that provides maps where keys are borrowed from values, reducing duplication and synchronization issues. It discusses the challenges of writing unsafe Rust code and how the library maintains correctness.
The author argues that memory-unsafe open-source software is critically vulnerable to upcoming AI bug-finding agents, making memory safety a moral imperative, and that Rust must succeed as the leading memory-safe language with no overhead.