New comment by n0blenote in "Recursion is lying to you"

n0blenote — Tue, 28 Jul 2026 22:32:14 +0000

I might not be understanding what you’re saying here… but recursion compared to your if/whiles, are inherently coupled to the shape of the type they traverse where in the prior two we define data comparisons or input sizes.

Using a jmp isn’t really a call as you’d know, and information is lost that would be crucial to unwinding a recursion.

A recurse keyword would still leave the person writing the code with the decision with proving termination with base cases or trampolines — lest there is just a bunch of math that would unwind your recursion into a better bounded problem. Which is kind of what current keywords do anyway.

New comment by n0blenote in "Zig's Incremental Compilation Internals"

n0blenote — Tue, 28 Jul 2026 22:15:30 +0000

I’m incredibly excited for this and have been looking forward to it for a while - I think new moves in IR will solve many issues with have with dynamic analysis of memory safety. The decompilation into other representations like Binary Ninjas IR have been a godsend to actually seeing what the hell Rust and Objective C do on the backend and understand actual cost the compiler makes to create memory fences.

Hacker News: n0blenote

New comment by n0blenote in "Recursion is lying to you"

New comment by n0blenote in "Zig's Incremental Compilation Internals"