Does pinning violate the wording in Constructors?

Open
#266 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Start with the quoted Constructors passage in the book and the issue's question about pinning. Verify whether the wording accurately distinguishes movable values from pinned values; done means resolving the question and identifying the precise documentation change, if one is needed.

Written by the indexing model from the issue text.

Description

The book says,

Move constructors are meaningless in Rust because we don't enable types to "care" about their location in memory. Every type must be ready for it to be blindly memcopied to somewhere else in memory. This means pure on-the-stack-but- still-movable intrusive linked lists are simply not happening in Rust (safely).

I'm new, but I'm not sure that's correct. Isn't that precisely what pin does?

Dominant language
CSS
Stars
2.3k
Forks
325
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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/nomicon

All issues in rust-lang/nomicon

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.