You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
…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.
Fixesrust-lang#5886
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: