C with Garbage Collection

Añadido: 2026-05-09

[00:00:00]Uh, hello, internet. So, uh, C is a language where you manage your own memory, right? malloc, free, dangling pointers, memory leaks, that's the deal. You get control, you take responsibility. But, what if the your compiler could offer you a second option, right? Heap-allocated data structures managed automatically, no freeing required.

[00:00:19]Uh, this is my C compiler. It compiles C to WebAssembly, and WebAssembly now has garbage collection. It's why I added it to C.

[00:00:28]Basic idea is this.

[00:00:29]A normal C program only uses linear memory, a a flat black block of bytes. You allocate with malloc, free with free, and use pointers to navigate that block.

[00:00:38]Wasm GC types live somewhere else entirely. They're on the man- engine's managed heap outside linear memory. You can't take their address, you can't embed them inside a normal normal C struct. They exist in a separate universe.

[00:00:51]It sounds respec- restrictive, and it is, but the trade-off is that you never you never free them. The engine handles it.

[00:01:00]So, let me let me show you what this looks like in practice.

[00:01:04]You declare a struct with uh double underscore struct. You allocate with new.

[00:01:11]Fields start zero-initialized, and you set them with arrow assignment. Just like a pointer to a struct in regular C.

[00:01:18]And that's intentional. A GC reference is conceptually a pointer. It refers to a heap object. The star and the arrow make that explicit. C23 introduces the auto keyword, which lets the compiler infer the variable's type. Uh, and together with a typedef, you can clean clean this up quite a bit. So, yeah, it looks uh it looks nice.

[00:01:39]Okay, so GC arrays.

[00:01:41]Uh, declare you declare the type with array int.

[00:01:45]Uh, you allocate with array new.

[00:01:48]And then you get the length with array len. You can access the elements using the the usual subscript syntax.

[00:01:57]Uh, you can also create arrays with array literals like this, literal values like this.

[00:02:03]And this compiles down to the array.new fixed uh opcode.

[00:02:11]Okay. So far our containers have have had a fixed element type, right? But sometimes you want one that holds anything like what uh like object in Java or or sort of like void star in in C, right? So WasmGC gives you a few choices of types for that, but but for us we're using anyref.

[00:02:30]So it's a supertype of every GC reference type we have, uh like structs and arrays, and box primitives.

[00:02:37]Uh and you you can also unbox through casting as well.

[00:02:41]So this turns out to be enough to build some really cool like uh generic containers that you you usually take for granted in other languages that are just hard to have in C. So here's the heart of a Java-style array list here.

[00:02:55]And yeah, so so this is how you would use it. Um I think looks pretty nice. Uh and yeah, the full source is in the compiler repo.