Managing Memory without a Garbage Collector: Understanding Rust's Borrow Checker
Learn how Rust eliminates data races and use-after-free errors without a garbage collector using its unique ownership and borrowing system.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Rust eliminates data races and use-after-free errors without a garbage collector using its unique ownership and borrowing system.
Explore how Jule implements zero-cost abstractions to provide systems-level performance without the overhead of a garbage collector.
Nim's Optimized Reference Counting (ORC) delivers deterministic destruction without a garbage collector, making it suitable for embedded, real‑time, and WASM targets. This post walks through how ORC works, a cyclic data‑structure example, and the trade‑offs you must accept.
Explore how Jule achieves memory safety without a garbage collector using ownership and borrow-checking to eliminate data races and memory leaks.
Jule compiles to C++ instead of machine code, trading custom backend maintenance for instant platform support and seamless C++ interop. Learn how this affects memory safety, debugging, and the build pipeline.
Carbon introduces checked pointers as a language-level mechanism to prevent null dereference at compile time, offering a safer alternative to raw C++ pointers while maintaining interoperability.
How Zig's comptime lets you run code at compile time for zero-overhead polymorphism and explicit error propagation.
Learn how to implement explicit memory management in Zig using the GeneralPurposeAllocator to eliminate leaks and manage dynamic memory with precision.
Learn how Jule uses move semantics to achieve memory safety and high performance without the overhead of a garbage collector.