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

unclear definition of lifetime input positions in RFC 39 #165

Closed
pnkfelix opened this issue Jul 15, 2014 · 0 comments · Fixed by #166
Closed

unclear definition of lifetime input positions in RFC 39 #165

pnkfelix opened this issue Jul 15, 2014 · 0 comments · Fixed by #166
Labels
T-lang Relevant to the language team, which will review and decide on the RFC.

Comments

@pnkfelix
Copy link
Member

As I noted here, the current definition for "lifetime input position" does not make it 100% clear that when it says that certain lifetimes in an impl are in input position, that is solely for the purposes of inferring output lifetimes for other parts of the impl header, and has absolutely no effect on the method definitions within the impl.

I hope to have a PR to fix this and a few other typos shortly.
@pnkfelix pnkfelix mentioned this issue Jul 15, 2014
Merged
@Centril Centril added the T-lang Relevant to the language team, which will review and decide on the RFC. label Feb 23, 2018
wycats pushed a commit to wycats/rust-rfcs that referenced this issue Mar 5, 2019
@rwjblue
Merge pull request rust-lang#165 from emberjs/locks-patch-1
8d3bf65 
typos
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-lang Relevant to the language team, which will review and decide on the RFC.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clarify definition of "input positions" in lifetime elision RFC. pnkfelix/rfcs
2 participants
@pnkfelix @Centril