diff options
| author | bors <bors@rust-lang.org> | 2017-01-13 16:59:25 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2017-01-13 16:59:25 +0000 |
| commit | 1d5fb06c3bb3318d7b2d6853839cb1750943770f (patch) | |
| tree | 10e41633b115e4a65a5a4193226495a50e642e1c /src/rustllvm/RustWrapper.cpp | |
| parent | b0c52c587fe9ba287053359fff5ed886b7edb27c (diff) | |
| parent | 2092682191f104c7764eba23d4317f4b7f98a100 (diff) | |
| download | rust-1d5fb06c3bb3318d7b2d6853839cb1750943770f.tar.gz rust-1d5fb06c3bb3318d7b2d6853839cb1750943770f.zip | |
Auto merge of #38890 - petrochenkov:noresolve, r=nrc
resolve: Do not use "resolve"/"resolution" in error messages Use less jargon-y wording instead. `cannot find <struct> <S> in <this scope>` and `cannot find <struct> <S> in <module a::b>` are used for base messages (this also harmonizes nicely with "you can import it into scope" suggestions) and `not found in <this scope>` and `not found in <a::b>` are used for short labels in fall-back case. I tweaked some other diagnostics to avoid using "resolve" (see, e.g., `librustc_resolve/macros.rs`), but haven't touched messages for imports. Closes https://github.com/rust-lang/rust/issues/38750 r? @nrc
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions