This is a short summary. ↗ Open original to view full content
Making C++ Memory-Safe Without Borrow Checking, Reference Counting, or Tracing Garbage Collection
from blog Languages and Architecture, | ↗ original
Related
More from Languages and Architecture
Crossing the Impossible FFI Boundary, and My Gradual Descent Into Madness
17 Jun 2024 |
original ↗
Committing language interop sins for science June 17, 2024 — Anyone trying to make a new mainstream language is completely insane, unless they're backed by a huge corporation.
Exploring Seamless Rust Interop for Newer Languages, Part 1
24 May 2024 |
original ↗
Committing language interop sins for science May 24, 2024 — Languages like C++, Typescript, Kotlin, and Swift had a brilliant approach: they were created to harness an existing ecosystem of libraries from another pre-existing language. But that's easier said than done!...
Higher RAII, and the Seven Arcane Uses of Linear Types
14 May 2024 |
original ↗
Linear types + whitelisted destroyers = powers yet unimagined! May 14, 2024 — Also posted today: Layer-wise inferencing + batching: Small VRAM doesn't limit LLM throughput anymore, on how even a normal small computer can now run...
Layer-wise inferencing + batching: Small VRAM doesn't limit LLM throughput anymore
14 May 2024 |
original ↗
Also posted today: Higher RAII, and the Seven Arcane Uses of Linear Types, about how linear types let us control the future! Currently, the general consensus is that you can't really run larger LLMs on ordinary computers.
Borrow checking, RC, GC, and the Eleven (!) Other Memory Safety Approaches
24 Apr 2024 |
original ↗
The Memory Safety Grimoire, Part 1 April 24, 2024 — A fellow named Zeke came into my server one day. Zeke: "Wait, so with generational references, we now have four ways to do memory safety?" Evan: "In fact, there are fourteen by my count....