| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-11-22 | Diagnostic for using macro_rules macro as attr/derive | clubby789 | -1/+7 | |
| 2024-09-02 | chore: Fix typos in 'compiler' (batch 2) | Alexander Cyon | -1/+1 | |
| 2024-07-12 | When finding item gated behind a `cfg` flat, point at it | Esteban 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-21 | Fix remaining cases | Michael Goulet | -1/+1 | |
| 2024-05-24 | And more general error | Michael Baikov | -1/+5 | |
| 2024-05-24 | A custom error message for lending iterators | Michael Baikov | -0/+4 | |
| 2024-04-13 | Reorder error messages | Jean CASPAR | -13/+6 | |
| 2024-04-13 | Migrate more diagnostics | Jean CASPAR | -0/+106 | |
| 2024-04-13 | Migrate some diagnostics | Jean CASPAR | -1/+1 | |
| 2024-04-13 | Port build_reduce_graph | JeanCASPAR | -2/+58 | |
| 2024-03-04 | Rollup 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-01 | Remove unused fluent messages | r0cky | -22/+0 | |
| 2024-02-29 | Suggest moving if non-found macro_rules! is defined later | yukang | -0/+7 | |
| 2024-02-06 | Rollup merge of #119939 - clubby789:static-const-generic-note, r=compiler-errors | Matthias Krüger | -2/+12 | |
| Improve 'generic param from outer item' error for `Self` and inside `static`/`const` items Fixes #109596 Fixes #119936 | ||||
| 2024-02-04 | Suggest `[tail @ ..]` on `[..tail]` and `[...tail]` where `tail` is unresolved | León Orell Valerian Liehr | -0/+3 | |
| 2024-02-02 | Suggest changing ty to const params if appropriate | León Orell Valerian Liehr | -0/+3 | |
| 2024-01-14 | Special case 'generic param from outer item' message for `Self` | clubby789 | -2/+8 | |
| 2024-01-14 | Add note to resolve error about generics from inside static/const | clubby789 | -0/+4 | |
| 2024-01-09 | Check bindings around never patterns | Nadrieril | -0/+4 | |
| 2023-12-06 | tip for define macro name after `macro_rules!` | bohan | -0/+2 | |
| 2023-12-01 | Auto merge of #115993 - bvanjoi:fix-115966, r=petrochenkov | bors | -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-01 | vis note for no pub reexports glob import | bohan | -2/+0 | |
| 2023-11-30 | generic_const_exprs: suggest to add the feature, not use it | Ralf Jung | -1/+1 | |
| 2023-09-20 | Cleanup unused messages in ftl files | yukang | -12/+0 | |
| 2023-09-11 | Rollup merge of #115744 - fmease:fix-e0401, r=compiler-errors | Matthias 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-10 | Make E0401 translatable | León Orell Valerian Liehr | -16/+13 | |
| 2023-09-04 | resolve: derive diag for undetermined macro resolution | bohan | -0/+4 | |
| 2023-06-25 | Add translatable diagnostic for import resolution strings | Tom 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-19 | Remove unreachable and untested suggestion for invalid span enum derive(Default) | Tom Martin | -3/+0 | |
| 2023-06-18 | Fix tidy | Tom Martin | -22/+21 | |
| 2023-06-18 | Add translatable diagnostic for various strings in ↵ | Tom Martin | -0/+13 | |
| resolve::unresolved_macro_suggestions | ||||
| 2023-06-18 | Add translatable diagnostic for cannot find in this scope | Tom Martin | -1/+4 | |
| 2023-06-18 | Add translatable diagnostic for invalid imports | Tom Martin | -0/+3 | |
| 2023-06-18 | Add translatable diagnostic for changing import binding | Tom Martin | -0/+3 | |
| 2023-05-25 | Ensure Fluent messages are in alphabetical order | clubby789 | -175/+175 | |
| 2023-05-11 | Improve error for `self: Box<self>` | clubby789 | -0/+4 | |
| 2023-05-05 | improve diagnostics and bless tests | Boxy | -2/+27 | |
| 2023-04-25 | Fix static string lints | clubby789 | -0/+7 | |
| 2023-04-24 | Rollup merge of #110255 - clubby789:proc-macro-test-help, r=jackh726 | Matthias Krüger | -0/+3 | |
| Suggest using integration tests for test crate using own proc-macro cc #110247 | ||||
| 2023-04-17 | Suggest using integration tests for proc-macros | clubby789 | -0/+3 | |
| 2023-04-12 | Rollup merge of #110153 - DaniPopes:compiler-typos, r=Nilstrieb | Matthias 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-10 | Auto merge of #109638 - NotStirred:suggest/non-derive, r=davidtwco | bors | -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-10 | Fix typos in compiler | DaniPopes | -1/+1 | |
| 2023-04-07 | Rewrite added diagnostics as translatable | Tom Martin | -0/+10 | |
| Start messages with lowercase | ||||
| 2023-04-04 | Deny `use`ing tool paths | clubby789 | -0/+4 | |
| 2023-03-11 | Simplify message paths | est31 | -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 | ||||
