-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
typeck::check::_match emits derived errors #5658
Labels
Comments
Fixed, pending #6103 |
@catamorphism is this fixed now? #6103 landed |
Oops, forgot to close this. |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Aug 11, 2020
…r=Manishearth Avoid or_fun_call for const_fn with no args Based on rust-lang#5682 by @lzutao This avoids a subset of false positives, specifically those related to `const fn`s that take no arguments. For the rest, a much more involved fix would be needed, see rust-lang/rust-clippy#5682 (comment). So this does *not* solve rust-lang#5658 changelog: Avoid triggering [`or_fun_call`] with `const fn`s that take no arguments. Fixes rust-lang#5886
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The pattern-match-checking code potentially prints out derived errors because it doesn't check for
ty_err
like the rest of the typechecker does. I have a branch that almost fixes this but I got distracted working on higher-priority bugs.The text was updated successfully, but these errors were encountered: