Why Nim 2.0 Defaults to ORC: Deterministic Memory Without a Tracing GC
Nim 2.0 defaults to ORC for deterministic memory management without a tracing GC. Learn how ARC and ORC work, when to choose each mode, and what trade-offs to expect.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Nim 2.0 defaults to ORC for deterministic memory management without a tracing GC. Learn how ARC and ORC work, when to choose each mode, and what trade-offs to expect.
Switching Nim from mark-and-sweep to ARC or ORC removes stop-the-world pauses but introduces new ownership rules. Learn how to choose the right --mm flag and avoid circular reference leaks.
Learn how to diagnose and fix memory leaks and reference cycles in Nim using ARC and ORC. This guide covers --debug:memleak, ownership annotations, and breaking cycles with {.weak.}.
Stop-the-world GC pauses can ruin real-time performance. Learn how Nim's ARC and ORC provide deterministic memory management and how to handle reference cycles.