trivial: if Vec::into_iter() mispelled the comments ?
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2.3k
- Forks
- 325
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/rust-lang/nomicon/blob/master/src/vec/vec-into-iter.md#L62
impl<T> Vec<T> {
pub fn into_iter(self) -> IntoIter<T> {
// Can't destructure Vec since it's Drop <=== if 'Drop' should be 'Copy' ?
let ptr = self.ptr;
let cap = self.cap;
let len = self.len;
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open src/vec/vec-into-iter.md around line 62 and inspect the comment in the Vec::into_iter example. Compare the use of “Drop” with the surrounding code and issue question, then correct the comment if the wording is wrong. Done means the example comment accurately describes why Vec cannot be destructured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100