การคัดลอกเทียบกับสถานะร่วม

Sometimes editing one variable also edits another, and sometimes it does not. The difference is copy versus shared state. 🔍

When you get a copy, you hold separate data. Editing it cannot reach back and disturb the value you copied from.

With shared state, two variables point at the same underlying data. A change through one is visible through the other.

Ask: after I edit one variable, did the other one change too? If yes, they shared; if no, you had a copy.

For value types, Mojo gives you a copy on assignment. So in everyday code, changes stay nicely contained.

Copy a struct and you copy each field inside it. The new struct is fully independent from the original.

Shared state means a distant edit can silently change your value. That spooky action at a distance is a classic source of bugs.

Sharing is not evil; sometimes you want one source of truth. The key is to choose it on purpose, not by accident.

When you see an assignment, picture whether it makes a copy or a link. That habit predicts how edits will travel.

Copy: edits stay put. Shared: edits ripple. Mojo's default leans toward copies, so ripples are the exception, not the rule.

Knowing copies are independent lets you change a value boldly, sure that other parts of your program stay stable. ✅

Two variables point at the same underlying data. You edit one. What do you expect?

A copy keeps edits contained; shared state lets them ripple. Mojo copies value types by default, so surprises are rare. 🎯