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

macro check for redundant_closure_call #1639

Closed
llogiq opened this issue Mar 26, 2017 · 2 comments
Closed

macro check for redundant_closure_call #1639

llogiq opened this issue Mar 26, 2017 · 2 comments
Labels
C-bug Category: Clippy is not doing the correct thing good-first-issue These issues are a good way to get started with Clippy T-middle Type: Probably requires verifiying types

Comments

@llogiq
Copy link
Contributor

llogiq commented Mar 26, 2017

libcore has a counter-example for redundant_closure_call: In str/pattern.rs,
a macro reuses type constructors as closures to create instances of Searchers
to easily abstract over Pattern types. A macro check would probably do good
here.
@oli-obk oli-obk added good-first-issue These issues are a good way to get started with Clippy C-bug Category: Clippy is not doing the correct thing T-middle Type: Probably requires verifiying types labels Mar 27, 2017
@clarfonthey
Copy link
Contributor

duplicate of #1553 ?

@phansch
Copy link
Member

phansch commented Apr 21, 2019

Closing as dup of #1553

@phansch phansch closed this as completed Apr 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-bug Category: Clippy is not doing the correct thing good-first-issue These issues are a good way to get started with Clippy T-middle Type: Probably requires verifiying types
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@oli-obk @Manishearth @phansch @llogiq @clarfonthey