diff options
| author | 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> | 2024-05-29 03:25:08 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-29 03:25:08 +0100 |
| commit | bc1a069ec54a71d57604dbcf4b5bf204cc068033 (patch) | |
| tree | a6074930f444990f8e921a93873cd5cc8d6a6a2f /compiler/rustc_errors/src/snippet.rs | |
| parent | 3cc59aeaaeddb6fa6c2723e4664f46a395d25e30 (diff) | |
| parent | 37c54db477b06ade1cb69b4fd1af46184b650a43 (diff) | |
| download | rust-bc1a069ec54a71d57604dbcf4b5bf204cc068033.tar.gz rust-bc1a069ec54a71d57604dbcf4b5bf204cc068033.zip | |
Rollup merge of #125381 - estebank:issue-96799, r=petrochenkov
Silence some resolve errors when there have been glob import errors When encountering `use foo::*;` where `foo` fails to be found, and we later encounter resolution errors, we silence those later errors. A single case of the above, for an *existing* import on a big codebase would otherwise have a huge number of knock-down spurious errors. Ideally, instead of a global flag to silence all subsequent resolve errors, we'd want to introduce an unnameable binding in the appropriate rib as a sentinel when there's a failed glob import, so when we encounter a resolve error we can search for that sentinel and if found, and only then, silence that error. The current approach is just a quick proof of concept to iterate over. Partially address #96799.
Diffstat (limited to 'compiler/rustc_errors/src/snippet.rs')
0 files changed, 0 insertions, 0 deletions
