Skip to content

false negative for disallowed-methods #9558

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

Closed
xxchan opened this issue Sep 30, 2022 · 0 comments · Fixed by #9495
Closed

false negative for disallowed-methods #9558

xxchan opened this issue Sep 30, 2022 · 0 comments · Fixed by #9495
Labels
C-bug Category: Clippy is not doing the correct thing I-false-negative Issue: The lint should have been triggered on code, but wasn't

Comments

@xxchan
Copy link
Contributor

xxchan commented Sep 30, 2022

Summary

use futures::stream::{empty, select_all};

fn main() {
    let _ = select_all(vec![empty::<()>()]);
}

with clippy.toml

disallowed-methods = [{ path = "futures::stream::select_all" }]

produces no warnings.

Since futures::stream is re-export of futures_util::stream, I also tried that but clippy didn't work neither.

Lint Name

disallowed-methods

Reproducer

No response

Version

rustc 1.64.0 (a55dd71d5 2022-09-19)
binary: rustc
commit-hash: a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52
commit-date: 2022-09-19
host: aarch64-apple-darwin
release: 1.64.0
LLVM version: 14.0.6
@xxchan xxchan added C-bug Category: Clippy is not doing the correct thing I-false-negative Issue: The lint should have been triggered on code, but wasn't labels Sep 30, 2022
@bors bors closed this as completed in e687bed Oct 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Clippy is not doing the correct thing I-false-negative Issue: The lint should have been triggered on code, but wasn't
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant