ความหมายของซีแมนติกส์แบบค่า

When you copy a value into a new variable, does each one stand alone, or do they secretly share? Value semantics answers that. 🤔

Under value semantics, every variable holds its very own copy of the data. No two names quietly point at the same thing.

Assigning b = a hands b a fresh copy. From that moment on, a and b live independent lives.

Because b owns its own copy, updating b never touches a. The original value stays exactly as you left it.

Picture each variable as its own box. Copying pours the contents into a second box, not a shortcut to the first.

Simple types like Int copy by value naturally. Pass x around and each spot gets its own number to work with.

Mojo applies value semantics broadly, even to structs you write. Copying a struct copies all of its fields too.

With value semantics you read code locally: a variable changes only when you change it, never as a side effect elsewhere. ✅

The opposite is reference behavior, where two names point at one object. Mojo prefers values to avoid that surprise by default.

The heart of value semantics is independence: copies are truly separate, so edits stay contained where you make them.

Independent values let Mojo reason about your program tightly, which helps it stay both safe and fast.

You write var b = a, then change b. What happens to a under value semantics?

With value semantics, every variable owns an independent copy. Changing one never ripples into another, which keeps code predictable. 🎯