Lifetime elision in trait constraints
Open
Nobody has claimed this yet.
T-lang
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Originally from https://github.com/rust-lang/rust/issues/13840:
This compiles:
fn isum<'a, I: Iterator<&'a i32>>(mut it: I) -> int { it.fold(0, |a, b| a + *b) }
This should be the same, but doesn't compile:
fn isum<I: Iterator<&i32>>(mut it: I) -> i32 { it.fold(0, |a, b| a + *b)}
The compiler complains of a "missing lifetime specifier" at the &int.
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
Start by reading the linked rust-lang/rust issue 13840 and comparing the two Iterator constraint examples in this issue. Determine the intended lifetime-elision behavior and how it should be specified and validated; the payload names no implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100