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

Lint checking for non-implicitly-copyable-typarams #5101

Closed

Conversation

tychosci
Copy link
Contributor

The lint checking for non-implicitly-copyable-typarams has somehow been removed at a380df8, but I don't think it is intentional.

@nikomatsakis
Copy link
Contributor

Actually, that was intentional. It was generally considered that this warning did more harm than good.

Perhaps though it is good to bring it back, and just change the default setting to disabled.

@tychosci
Copy link
Contributor Author

Ahh, I see. Thanks! If that was intentional, I have nothing to say against it.

@tychosci tychosci closed this Feb 26, 2013
bors added a commit to rust-lang-ci/rust that referenced this pull request May 2, 2020
add `let_underscore_lock` lint

closes rust-lang#1574
changelog: add `let_underscore_lock` lint

I am not entirely sure about my docs/messages wording here, improvements are welcome
flip1995 pushed a commit to flip1995/rust that referenced this pull request Nov 20, 2020
Add `let_underscore_drop`

This line generalizes `let_underscore_lock` (rust-lang#5101) to warn about any initializer expression that implements `Drop`.

So, for example, the following would generate a warning:
```rust
struct Droppable;
impl Drop for Droppable {
    fn drop(&mut self) {}
}
let _ = Droppable;
```

I tried to preserve the original `let_underscore_lock` functionality in the sense that the warning generated for
```rust
let _ = mutex.lock();
```
should be unchanged.

*Please keep the line below*
changelog: Add lint [`let_underscore_drop`]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants