https://blog.mickeyzzc.tech/en/tags/ownership/Recent content in Ownership on Mi&Bee BlogHugo -- gohugo.ioen蓝宝石的傻话Wed, 06 May 2026 10:00:00 +0800https://blog.mickeyzzc.tech/en/posts/programming/rust-ownership-borrowing/Wed, 06 May 2026 10:00:00 +0800https://blog.mickeyzzc.tech/en/posts/programming/rust-ownership-borrowing/<p>This article is based on Rust 1.80+.</p> <p>If you have a Go or Java background, the ownership system might be the most confusing concept in Rust. Go has a garbage collector (GC), and you rarely need to worry about when memory is freed. Rust takes a completely different approach—<strong>compile-time ownership rules guarantee memory safety</strong>, with zero runtime overhead.</p> <blockquote> <p><strong>The ownership system is the soul of Rust</strong>. It solves two classic problems: how to guarantee memory safety <strong>without using GC</strong>, and how to <strong>avoid data races</strong>. In other languages, these problems either require runtime checks or require extreme developer caution.</p>