3.1 Structures "because we used that field from `point`" should be "`another_point`"

Open Beginner friendly
#1,846 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Search the repository for the quoted comment in the Structures example. Change the reference from point to another_point, then verify that the example's displayed output remains consistent with the corrected explanation.

Written by the indexing model from the issue text.

Description

At least, I'm pretty sure.
Line for reference:

    // Instantiate a `Point`
    let point: Point = Point { x: 10.3, y: 0.4 };
    let another_point: Point = Point { x: 5.2, y: 0.2 };

    // Access the fields of the point
    println!("point coordinates: ({}, {})", point.x, point.y);

    // Make a new point by using struct update syntax to use the fields of our
    // other one
    let bottom_right = Point { x: 5.2, ..another_point };

    // `bottom_right.y` will be the same as `point.y` because we used that field
    // from `point`
    println!("second point: ({}, {})", bottom_right.x, bottom_right.y);

Which prints

point coordinates: (10.3, 0.4)
second point: (5.2, 0.2)

As you can see, it is the same as another_point.y, and not point.y :)

Dominant language
Handlebars
Stars
8.1k
Forks
1.6k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/rust-by-example

All issues in rust-lang/rust-by-example

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.