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
There is code that deduplicates problems, however it only kicks in if the problems are exactly the same, including all usages. Where two binaries in your dependency graph both depend on the same crate, you can end up with the same problem reported twice, but with usages that aren't exactly the same. The usages depend on code reachability, so if different functions are reachable in the two crates, then the usages will be different.
Probably to make the duplicates completely go away, I'll need to actually merge the problems together, which is made slightly tricky because internally I need to keep the original problems. The threads that reported each problem are waiting for all problems they reported to be resolved before they allow that bit of compilation to complete.
Noticed that on our big project the same "problem" gets listed multiple times, which is confusing. Example:
we are using:
is this an artifact of how the tool works, or is it missing some de-duplication in its analysis or display?
The text was updated successfully, but these errors were encountered: