In this lesson, you will learn how to distinguish between giving a name to a memory location and the act of moving ownership of the data residing within it.
Binding: The Labeling Process
In Rust, when you write let x = 5;, you are creating a variable binding. Think of this as putting a sticky note labeled x on a specific location in memory that holds the value 5. The variable x is simply the name we use to refer to that data.
Assignment: The Ownership Transfer
When we move beyond simple integers—which are copied by default—and look at heap-allocated resources (like a String), the concept of Data Assignment changes. In Rust, assigning a variable to a new variable is an "ownership transfer."
Consider this example:
let s1 = String::from("Hello"); // Binding: s1 owns the heap data.
let s2 = s1; // Assignment: The data moves from s1 to s2.
In the code above, s1 is a binding. When we write let s2 = s1;, we aren't just copying the label; we are transferring the "ownership" of the underlying heap data to s2. Because the data has been moved, the original binding s1 is now considered uninitialized. If you try to use s1 again, the compiler will stop you.
Why is this distinct?
- Variable Binding is about human-readable naming. It identifies where the data lives in the stack frame.
- Data Assignment (in the context of ownership) is a structural operation. It determines who has the right to manage the lifetime of the data.
When you assign s1 to s2, the memory location holding the "pointer" to the heap is copied to s2, and s1 is invalidated. This ensures that only one variable is responsible for cleaning up the memory, preventing the double-free errors common in other languages. You are not just updating a value; you are shifting the responsibility of the resource.
Key Takeaway: Variable binding names a location, but data assignment—for non-copyable types—transfers the exclusive ownership of the underlying resource to a new name.