Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Mention move of individual struct fields in struct update syntax #4046

Merged
merged 3 commits into from
Oct 2, 2024
Merged

Mention move of individual struct fields in struct update syntax #4046

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
88c3e55
Mention move of individual struct fields
jpmelos Sep 29, 2024
b82de7e
Revert "Mention move of individual struct fields"
jpmelos Oct 1, 2024
26bea11
Add note about field access after struct update syntax
jpmelos Oct 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/ch05-01-defining-structs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,7 +154,8 @@ Move”][move]<!-- ignore --> section. In this example, we can no longer use
`active` and `sign_in_count` values from `user1`, then `user1` would still be
valid after creating `user2`. Both `active` and `sign_in_count` are types that
implement the `Copy` trait, so the behavior we discussed in the [“Stack-Only
Data: Copy”][copy]<!-- ignore --> section would apply.
Data: Copy”][copy]<!-- ignore --> section would apply. We can still use
`user1.email` in this example, since its value was _not_ moved out.

### Using Tuple Structs Without Named Fields to Create Different Types

Expand Down