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

Don't warn about instantiating a copy type parameter with a non-implicitly-copyable type when the receiver is the only one with the type parameter #2542

Closed
pcwalton opened this issue Jun 8, 2012 · 0 comments
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. A-typesystem Area: The type system C-enhancement Category: An issue proposing an enhancement or a PR with one.

Comments

@pcwalton
Copy link
Contributor

pcwalton commented Jun 8, 2012

hashmap.contains_key("foo") shouldn't warn, because the type parameters are only in the receiver.

flip1995 pushed a commit to flip1995/rust that referenced this issue Jul 17, 2020
flip1995 pushed a commit to flip1995/rust that referenced this issue Jul 17, 2020
Add test for `needless_range_loop` issue

Closes rust-lang#2277

This was fixed when we fixed rust-lang#2542.

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue Sep 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-lint Area: Lints (warnings about flaws in source code) such as unused_mut. A-typesystem Area: The type system C-enhancement Category: An issue proposing an enhancement or a PR with one.
Projects
None yet
Development

No branches or pull requests

1 participant