Feature request: Silence not-found error when a suggested import is already in-place but typo'd #84093
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
D-verbose
Diagnostics: Too much output caused by a single piece of incorrect code.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
When trying to import and then use an item, but there is a typo in the import (which rustc successfully provides a suggestion for), I think the usage of the item should not trigger a not-found error. Example with a trait method (playground):
Currently triggers two errors, with the second one being redundant IMO:
The text was updated successfully, but these errors were encountered: