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.

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

Make elision better #18

Closed
Manishearth opened this issue Nov 23, 2014 · 2 comments
Closed

Make elision better #18

Manishearth opened this issue Nov 23, 2014 · 2 comments
Labels
S-needs-discussion Status: Needs further discussion before merging or work can be started

Comments

@Manishearth
Copy link
Member

I wonder if we can catch cases like these where elision breaks things.

Basically, when the returned value has no relation to the inputs, lint that elision might not be wanted.

Exact heuristics would be tough to figure out, but I think it's doable (I've got a rough idea)

Ideally this should go into the compiler, but we can start it as a lint.

@Manishearth Manishearth added E-hard Call for participation: This a hard problem and requires more experience or effort to work on S-needs-discussion Status: Needs further discussion before merging or work can be started and removed E-hard Call for participation: This a hard problem and requires more experience or effort to work on labels Aug 11, 2015
@felix91gr
Copy link
Contributor

Since lifetime elision's gone a long way from 2014 to today, is this still an issue?

yaahc pushed a commit to yaahc/rust-clippy that referenced this issue Mar 14, 2019
@camsteffen
Copy link
Contributor

Closing in favor of #305

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-needs-discussion Status: Needs further discussion before merging or work can be started
Projects
None yet
Development

No branches or pull requests

3 participants