about summary refs log tree commit diff
path: root/compiler/rustc_resolve/messages.ftl
AgeCommit message (Collapse)AuthorLines
2024-11-22Diagnostic for using macro_rules macro as attr/deriveclubby789-1/+7
2024-09-02chore: Fix typos in 'compiler' (batch 2)Alexander Cyon-1/+1
2024-07-12When finding item gated behind a `cfg` flat, point at itEsteban Küber-0/+2
Previously we would only mention that the item was gated out, and opportunisitically mention the feature flag name when possible. We now point to the place where the item was gated, which can be behind layers of macro indirection, or in different modules. ``` error[E0433]: failed to resolve: could not find `doesnt_exist` in `inner` --> $DIR/diagnostics-cross-crate.rs:18:23 | LL | cfged_out::inner::doesnt_exist::hello(); | ^^^^^^^^^^^^ could not find `doesnt_exist` in `inner` | note: found an item that was configured out --> $DIR/auxiliary/cfged_out.rs:6:13 | LL | pub mod doesnt_exist { | ^^^^^^^^^^^^ note: the item is gated here --> $DIR/auxiliary/cfged_out.rs:5:5 | LL | #[cfg(FALSE)] | ^^^^^^^^^^^^^ ```
2024-06-21Fix remaining casesMichael Goulet-1/+1
2024-05-24And more general errorMichael Baikov-1/+5
2024-05-24A custom error message for lending iteratorsMichael Baikov-0/+4
2024-04-13Reorder error messagesJean CASPAR-13/+6
2024-04-13Migrate more diagnosticsJean CASPAR-0/+106
2024-04-13Migrate some diagnosticsJean CASPAR-1/+1
2024-04-13Port build_reduce_graphJeanCASPAR-2/+58
2024-03-04Rollup merge of #121130 - chenyukang:yukang-fix-121061-macro-later, ↵Matthias Krüger-0/+7
r=matthiaskrgr Suggest moving definition if non-found macro_rules! is defined later Fixes #121061
2024-03-01Remove unused fluent messagesr0cky-22/+0
2024-02-29Suggest moving if non-found macro_rules! is defined lateryukang-0/+7
2024-02-06Rollup merge of #119939 - clubby789:static-const-generic-note, r=compiler-errorsMatthias Krüger-2/+12
Improve 'generic param from outer item' error for `Self` and inside `static`/`const` items Fixes #109596 Fixes #119936
2024-02-04Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolvedLeón Orell Valerian Liehr-0/+3
2024-02-02Suggest changing ty to const params if appropriateLeón Orell Valerian Liehr-0/+3
2024-01-14Special case 'generic param from outer item' message for `Self`clubby789-2/+8
2024-01-14Add note to resolve error about generics from inside static/constclubby789-0/+4
2024-01-09Check bindings around never patternsNadrieril-0/+4
2023-12-06tip for define macro name after `macro_rules!`bohan-0/+2
2023-12-01Auto merge of #115993 - bvanjoi:fix-115966, r=petrochenkovbors-2/+0
vis note for no pub reexports glob import Fixes #115966 Only trigger the `unused_import` lint when it's not being used. r? `@petrochenkov`
2023-12-01vis note for no pub reexports glob importbohan-2/+0
2023-11-30generic_const_exprs: suggest to add the feature, not use itRalf Jung-1/+1
2023-09-20Cleanup unused messages in ftl filesyukang-12/+0
2023-09-11Rollup merge of #115744 - fmease:fix-e0401, r=compiler-errorsMatthias Krüger-16/+13
Improve diagnostic for generic params from outer items (E0401) Generalize the wording of E0401 to talk about *outer items* instead of *outer functions* since the current phrasing is outdated. The outer item can be a function, constant, trait, ADT or impl block (see the new UI test for the more exotic examples). Further, don't suggest introducing generic parameters to constant items unless the feature `generic_const_items` is enabled. Lastly, make E0401 translatable while we're at it. Fixes #115720.
2023-09-10Make E0401 translatableLeón Orell Valerian Liehr-16/+13
2023-09-04resolve: derive diag for undetermined macro resolutionbohan-0/+4
2023-06-25Add translatable diagnostic for import resolution stringsTom Martin-0/+38
Add translatable diagnostic for cannot be reexported error also added for subdiagnostics Add translatable diagnostics for resolve_glob_import errors Add translatable diag for unable to determine import resolution Add translatable diag for is not directly importable
2023-06-19Remove unreachable and untested suggestion for invalid span enum derive(Default)Tom Martin-3/+0
2023-06-18Fix tidyTom Martin-22/+21
2023-06-18Add translatable diagnostic for various strings in ↵Tom Martin-0/+13
resolve::unresolved_macro_suggestions
2023-06-18Add translatable diagnostic for cannot find in this scopeTom Martin-1/+4
2023-06-18Add translatable diagnostic for invalid importsTom Martin-0/+3
2023-06-18Add translatable diagnostic for changing import bindingTom Martin-0/+3
2023-05-25Ensure Fluent messages are in alphabetical orderclubby789-175/+175
2023-05-11Improve error for `self: Box<self>`clubby789-0/+4
2023-05-05improve diagnostics and bless testsBoxy-2/+27
2023-04-25Fix static string lintsclubby789-0/+7
2023-04-24Rollup merge of #110255 - clubby789:proc-macro-test-help, r=jackh726Matthias Krüger-0/+3
Suggest using integration tests for test crate using own proc-macro cc #110247
2023-04-17Suggest using integration tests for proc-macrosclubby789-0/+3
2023-04-12Rollup merge of #110153 - DaniPopes:compiler-typos, r=NilstriebMatthias Krüger-1/+1
Fix typos in compiler I ran [`typos -w compiler`](https://github.com/crate-ci/typos) to fix typos in the `compiler` directory. Refs #110150
2023-04-10Auto merge of #109638 - NotStirred:suggest/non-derive, r=davidtwcobors-0/+10
Add suggestion to remove `derive()` if invoked macro is non-derive Adds to the existing `expected derive macro, found {}` error message: ``` help: remove the surrounding "derive()": --> $DIR/macro-path-prelude-fail-4.rs:1:3 | LL | #[derive(inline)] | ^^^^^^^ ^ ``` This suggestion will either fix the issue, in the case that the macro was valid, or provide a better error message if not Not ready for merge yet, as the highlighted span is only valid for trivial formatting. Is there a nice way to get the parent span of the macro path within `smart_resolve_macro_path`? Closes #109589
2023-04-10Fix typos in compilerDaniPopes-1/+1
2023-04-07Rewrite added diagnostics as translatableTom Martin-0/+10
Start messages with lowercase
2023-04-04Deny `use`ing tool pathsclubby789-0/+4
2023-03-11Simplify message pathsest31-0/+211
This makes it easier to open the messages file while developing on features. The commit was the result of automatted changes: for p in compiler/rustc_*; do mv $p/locales/en-US.ftl $p/messages.ftl; rmdir $p/locales; done for p in compiler/rustc_*; do sed -i "s#\.\./locales/en-US.ftl#../messages.ftl#" $p/src/lib.rs; done