mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
c19d56c902
rust/tests/ui-fulldeps/session-diagnostic/subdiagnostic-derive.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

574 lines
17 KiB
Plaintext
Raw Normal View History

give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): label without `#[primary_span]` field
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:51:1
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
LL | #[label(no_crate_example)]
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): diagnostic slug must be first argument of a `#[label(...)]` attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:58:1
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[label]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[foo]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:67:1
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[foo]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[label = ...]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:77:1
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[label = "..."]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): only `no_span` is a valid nested attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:86:9
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[label(bug = "...")]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^^^
Extract subdiagnostic attribute parsing
2022-09-12 13:44:28 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): diagnostic slug must be first argument of a `#[label(...)]` attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:86:1
macros: add helper functions for invalid attrs Remove some duplicated code between both diagnostic derives by introducing helper functions for reporting an error in case of a invalid attribute. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 22:06:13 -05:00
|
Extract subdiagnostic attribute parsing
2022-09-12 13:44:28 -05:00
LL | #[label(bug = "...")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): only `no_span` is a valid nested attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:106:9
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[label(slug = 4)]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^^^^
Extract subdiagnostic attribute parsing
2022-09-12 13:44:28 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): diagnostic slug must be first argument of a `#[label(...)]` attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:106:1
macros: use typed identifiers in subdiag derive As in the diagnostic derive, using typed identifiers in the subdiagnostic derive improves the diagnostics of using the subdiagnostic derive as Fluent messages will be confirmed to exist at compile-time. Signed-off-by: David Wood <david.wood@huawei.com>
2022-06-23 10:12:52 -05:00
|
Extract subdiagnostic attribute parsing
2022-09-12 13:44:28 -05:00
LL | #[label(slug = 4)]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): only `no_span` is a valid nested attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:116:9
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[label(slug("..."))]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^^^^
Extract subdiagnostic attribute parsing
2022-09-12 13:44:28 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): diagnostic slug must be first argument of a `#[label(...)]` attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:116:1
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
Extract subdiagnostic attribute parsing
2022-09-12 13:44:28 -05:00
LL | #[label(slug("..."))]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): diagnostic slug must be first argument of a `#[label(...)]` attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:136:1
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[label()]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): only `no_span` is a valid nested attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:145:27
macros: use typed identifiers in subdiag derive As in the diagnostic derive, using typed identifiers in the subdiagnostic derive improves the diagnostics of using the subdiagnostic derive as Fluent messages will be confirmed to exist at compile-time. Signed-off-by: David Wood <david.wood@huawei.com>
2022-06-23 10:12:52 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[label(no_crate_example, code = "...")]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^^^^
macros: use typed identifiers in subdiag derive As in the diagnostic derive, using typed identifiers in the subdiagnostic derive improves the diagnostics of using the subdiagnostic derive as Fluent messages will be confirmed to exist at compile-time. Signed-off-by: David Wood <david.wood@huawei.com>
2022-06-23 10:12:52 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): only `no_span` is a valid nested attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:154:27
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[label(no_crate_example, applicability = "machine-applicable")]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^^^^^^^^^^^^^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): unsupported type attribute for subdiagnostic enum
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:163:1
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[foo]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[bar]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:177:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[bar = ...]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:189:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar = "..."]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[bar = ...]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:201:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar = 4]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[bar(...)]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:213:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar("...")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): only `no_span` is a valid nested attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:225:13
Extract subdiagnostic attribute parsing
2022-09-12 13:44:28 -05:00
|
LL | #[label(code = "...")]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^^^^
Extract subdiagnostic attribute parsing
2022-09-12 13:44:28 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): diagnostic slug must be first argument of a `#[label(...)]` attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:225:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[label(code = "...")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): the `#[primary_span]` attribute can only be applied to fields of type `Span` or `MultiSpan`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:254:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[primary_span]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): label without `#[primary_span]` field
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:251:1
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
LL | #[label(no_crate_example)]
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[applicability]` is only valid on suggestions
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:264:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[applicability]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[bar]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:274:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: add helper functions for invalid attrs Remove some duplicated code between both diagnostic derives by introducing helper functions for reporting an error in case of a invalid attribute. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 22:06:13 -05:00
|
= help: only `primary_span`, `applicability` and `skip_arg` are valid field attributes
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[bar = ...]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:285:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar = "..."]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[bar(...)]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:296:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar("...")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
= help: only `primary_span`, `applicability` and `skip_arg` are valid field attributes
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): a diagnostic slug must be the first argument to the attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:328:44
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[label(no_crate_example, no_crate::example)]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): attribute specified multiple times
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:341:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[primary_span]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
note: previously specified here
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:338:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[primary_span]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): subdiagnostic kind not specified
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:347:8
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
macros: use typed identifiers in subdiag derive As in the diagnostic derive, using typed identifiers in the subdiagnostic derive improves the diagnostics of using the subdiagnostic derive as Fluent messages will be confirmed to exist at compile-time. Signed-off-by: David Wood <david.wood@huawei.com>
2022-06-23 10:12:52 -05:00
LL | struct AG {
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
| ^^
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): attribute specified multiple times
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:384:46
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "...", code = "...")]
fix errors
2023-04-03 10:11:30 -05:00
| ^^^^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
note: previously specified here
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:384:32
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "...", code = "...")]
fix errors
2023-04-03 10:11:30 -05:00
| ^^^^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): attribute specified multiple times
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:402:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[applicability]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
note: previously specified here
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:399:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[applicability]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): the `#[applicability]` attribute can only be applied to fields of type `Applicability`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:412:5
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[applicability]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): suggestion without `code = "..."`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:425:1
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example)]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): invalid applicability
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:435:62
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "...", applicability = "foo")]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^^^^^
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): suggestion without `#[primary_span]` field
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:453:1
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
|
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
LL | #[suggestion(no_crate_example, code = "...")]
| ^
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): unsupported type attribute for subdiagnostic enum
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:467:1
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[label]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `var` doesn't refer to a field on this type
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:487:39
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "{var}", applicability = "machine-applicable")]
| ^^^^^^^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `var` doesn't refer to a field on this type
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:506:43
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "{var}", applicability = "machine-applicable")]
| ^^^^^^^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[suggestion_part]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:529:5
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[suggestion_part]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
= help: `#[suggestion_part(...)]` is only valid in multipart suggestions, use `#[primary_span]` instead
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[suggestion_part(...)]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:532:5
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[suggestion_part(code = "...")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
= help: `#[suggestion_part(...)]` is only valid in multipart suggestions
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): suggestion without `#[primary_span]` field
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:526:1
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
|
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
LL | #[suggestion(no_crate_example, code = "...")]
| ^
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): invalid nested attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:541:42
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[multipart_suggestion(no_crate_example, code = "...", applicability = "machine-applicable")]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^^^^
Extract subdiagnostic attribute parsing
2022-09-12 13:44:28 -05:00
|
Use translatable diagnostics in `rustc_const_eval`
2023-05-17 05:30:14 -05:00
= help: only `no_span`, `style` and `applicability` are valid nested attributes
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): multipart suggestion without any `#[suggestion_part(...)]` fields
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:541:1
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
|
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
LL | #[multipart_suggestion(no_crate_example, code = "...", applicability = "machine-applicable")]
| ^
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[suggestion_part(...)]` attribute without `code = "..."`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:551:5
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
|
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
LL | #[suggestion_part]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[suggestion_part(...)]` attribute without `code = "..."`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:559:5
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[suggestion_part()]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[primary_span]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:568:5
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[primary_span]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
= help: multipart suggestions use one or more `#[suggestion_part]`s rather than one `#[primary_span]`
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): multipart suggestion without any `#[suggestion_part(...)]` fields
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:565:1
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
LL | #[multipart_suggestion(no_crate_example)]
| ^
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[suggestion_part(...)]` attribute without `code = "..."`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:576:5
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
|
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
LL | #[suggestion_part]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[suggestion_part(...)]` attribute without `code = "..."`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:579:5
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
|
LL | #[suggestion_part()]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `code` is the only valid nested attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:582:23
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
|
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
LL | #[suggestion_part(foo = "bar")]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^^^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): the `#[suggestion_part(...)]` attribute can only be applied to fields of type `Span` or `MultiSpan`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:587:5
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[suggestion_part(code = "...")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): the `#[suggestion_part(...)]` attribute can only be applied to fields of type `Span` or `MultiSpan`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:590:5
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[suggestion_part()]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): attribute specified multiple times
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:598:37
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[suggestion_part(code = "...", code = ",,,")]
fix errors
2023-04-03 10:11:30 -05:00
| ^^^^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
note: previously specified here
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:598:23
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[suggestion_part(code = "...", code = ",,,")]
fix errors
2023-04-03 10:11:30 -05:00
| ^^^^
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[applicability]` has no effect if all `#[suggestion]`/`#[multipart_suggestion]` attributes have a static `applicability = "..."`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:627:5
Revert parts of "use derive proc macro to impl SessionDiagnostic" This reverts parts of commit ac638c1f5fca36484506415319ab254ad522a692. During rebase, this commit accidentally reverted unrelated changes to the subdiagnostic derive (those allowing multipart_suggestions to be derived). This commit reverts all changes to the subdiagnostic code made in ac638c1f5fc, the next commit will reintroduce the actually intended changes.
2022-09-01 12:42:49 -05:00
|
LL | #[applicability]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Rework SessionSubdiagnostic derive to support multipart_suggestion
2022-08-23 00:54:06 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): expected exactly one string literal for `code = ...`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:675:34
Allow specifying multiple alternative suggestions This allows porting uses of span_suggestions() to diagnostic structs. Doesn't work for multipart_suggestions() because the rank would be reversed - the struct would specify multiple spans, each of which has multiple possible replacements, while multipart_suggestions() creates multiple possible replacements, each with multiple spans.
2022-10-17 12:41:49 -05:00
|
LL | #[suggestion_part(code("foo"))]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): expected exactly one string literal for `code = ...`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:686:41
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
|
LL | #[suggestion_part(code("foo", "bar"))]
| ^
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): expected exactly one string literal for `code = ...`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:697:30
Allow specifying multiple alternative suggestions This allows porting uses of span_suggestions() to diagnostic structs. Doesn't work for multipart_suggestions() because the rank would be reversed - the struct would specify multiple spans, each of which has multiple possible replacements, while multipart_suggestions() creates multiple possible replacements, each with multiple spans.
2022-10-17 12:41:49 -05:00
|
LL | #[suggestion_part(code(3))]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): expected exactly one string literal for `code = ...`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:708:29
Allow specifying multiple alternative suggestions This allows porting uses of span_suggestions() to diagnostic structs. Doesn't work for multipart_suggestions() because the rank would be reversed - the struct would specify multiple spans, each of which has multiple possible replacements, while multipart_suggestions() creates multiple possible replacements, each with multiple spans.
2022-10-17 12:41:49 -05:00
|
LL | #[suggestion_part(code())]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^
Allow specifying multiple alternative suggestions This allows porting uses of span_suggestions() to diagnostic structs. Doesn't work for multipart_suggestions() because the rank would be reversed - the struct would specify multiple spans, each of which has multiple possible replacements, while multipart_suggestions() creates multiple possible replacements, each with multiple spans.
2022-10-17 12:41:49 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): attribute specified multiple times
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:763:1
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "", style = "hidden", style = "normal")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
note: previously specified here
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:763:1
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "", style = "hidden", style = "normal")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[suggestion_hidden(...)]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:772:1
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion_hidden(no_crate_example, code = "")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
Remove #[suggestion_*] attributes
2022-10-22 10:21:11 -05:00
= help: Use `#[suggestion(..., style = "hidden")]` instead
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[suggestion_hidden(...)]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:780:1
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion_hidden(no_crate_example, code = "", style = "normal")]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Remove #[suggestion_*] attributes
2022-10-22 10:21:11 -05:00
|
= help: Use `#[suggestion(..., style = "hidden")]` instead
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): invalid suggestion style
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:788:51
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "", style = "foo")]
| ^^^^^
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
Add "tool-only" suggestion style
2022-10-20 14:17:14 -05:00
= help: valid styles are `normal`, `short`, `hidden`, `verbose` and `tool-only`
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): expected `= "xxx"`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:796:49
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "", style = 42)]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): a diagnostic slug must be the first argument to the attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:804:48
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
LL | #[suggestion(no_crate_example, code = "", style)]
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
| ^
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): expected `= "xxx"`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:812:48
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
|
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
LL | #[suggestion(no_crate_example, code = "", style("foo"))]
| ^
Add style= parameter to suggestion attributes
2022-10-20 13:28:24 -05:00
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): `#[primary_span]` is not a valid attribute
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:825:5
Forbid #[suggestion_*(...)] on Vecs It is ambiguous whether this should produce several `.span_suggestions()` calls or one `.multipart_suggestions()` call.
2022-10-16 09:15:39 -05:00
|
LL | #[primary_span]
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
| ^
Forbid #[suggestion_*(...)] on Vecs It is ambiguous whether this should produce several `.span_suggestions()` calls or one `.multipart_suggestions()` call.
2022-10-16 09:15:39 -05:00
|
= note: there must be exactly one primary span
= help: to create a suggestion with multiple spans, use `#[multipart_suggestion]` instead
give a better error for tuple structs in `derive(Diagnostic)`
2023-12-24 17:34:31 -06:00
error: derive(Diagnostic): suggestion without `#[primary_span]` field
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:822:1
Forbid #[suggestion_*(...)] on Vecs It is ambiguous whether this should produce several `.span_suggestions()` calls or one `.multipart_suggestions()` call.
2022-10-16 09:15:39 -05:00
|
Bump `proc-macro2`, `syn` and `quote` This disables the `proc_macro_span` feature which unfortunately makes our diagnostic derive macro diagnostics a little worse.
2024-01-29 06:18:30 -06:00
LL | #[suggestion(no_crate_example, code = "")]
| ^
Forbid #[suggestion_*(...)] on Vecs It is ambiguous whether this should produce several `.span_suggestions()` calls or one `.multipart_suggestions()` call.
2022-10-16 09:15:39 -05:00
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
error[E0433]: failed to resolve: you might be missing crate `core`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:96:9
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
|
LL | #[label("...")]
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
| ^^^^^ you might be missing crate `core`
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
error[E0433]: failed to resolve: you might be missing crate `core`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:312:1
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
|
LL | union AC {
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
| ^^^^^ you might be missing crate `core`
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
error[E0433]: failed to resolve: you might be missing crate `core`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:582:27
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
|
LL | #[suggestion_part(foo = "bar")]
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
| ^ you might be missing crate `core`
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
error[E0433]: failed to resolve: you might be missing crate `core`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:675:28
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
|
LL | #[suggestion_part(code("foo"))]
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
| ^^^^^ you might be missing crate `core`
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
error[E0433]: failed to resolve: you might be missing crate `core`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:686:28
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
|
LL | #[suggestion_part(code("foo", "bar"))]
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
| ^^^^^ you might be missing crate `core`
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
error[E0433]: failed to resolve: you might be missing crate `core`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:697:28
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
|
LL | #[suggestion_part(code(3))]
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
| ^ you might be missing crate `core`
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
error[E0433]: failed to resolve: you might be missing crate `core`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:720:30
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
|
LL | #[suggestion_part(code = 3)]
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
| ^ you might be missing crate `core`
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
error[E0433]: failed to resolve: you might be missing crate `core`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:812:48
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
|
LL | #[suggestion(no_crate_example, code = "", style("foo"))]
Do not use question as label We don't want to have questions in the diagnostic output. Instead, we use wording that communicates uncertainty, like "might": ``` error[E0432]: unresolved import `spam` --> $DIR/import-from-missing-star-3.rs:2:9 | LL | use spam::*; | ^^^^ you might be missing crate `spam` | = help: consider adding `extern crate spam` to use the `spam` crate ```
2024-07-23 14:43:46 -05:00
| ^ you might be missing crate `core`
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
error: cannot find attribute `foo` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:67:3
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[foo]
| ^^^
error: cannot find attribute `foo` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:163:3
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[foo]
| ^^^
error: cannot find attribute `bar` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:177:7
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar]
| ^^^
error: cannot find attribute `bar` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:189:7
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar = "..."]
| ^^^
error: cannot find attribute `bar` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:201:7
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar = 4]
| ^^^
error: cannot find attribute `bar` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:213:7
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar("...")]
| ^^^
error: cannot find attribute `bar` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:274:7
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar]
| ^^^
error: cannot find attribute `bar` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:285:7
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar = "..."]
| ^^^
error: cannot find attribute `bar` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:296:7
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
|
LL | #[bar("...")]
| ^^^
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
error[E0425]: cannot find value `slug` in module `crate::fluent_generated`
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:126:9
macros: use typed identifiers in subdiag derive As in the diagnostic derive, using typed identifiers in the subdiagnostic derive improves the diagnostics of using the subdiagnostic derive as Fluent messages will be confirmed to exist at compile-time. Signed-off-by: David Wood <david.wood@huawei.com>
2022-06-23 10:12:52 -05:00
|
LL | #[label(slug)]
errors: generate typed identifiers in each crate Instead of loading the Fluent resources for every crate in `rustc_error_messages`, each crate generates typed identifiers for its own diagnostics and creates a static which are pulled together in the `rustc_driver` crate and provided to the diagnostic emitter. Signed-off-by: David Wood <david.wood@huawei.com>
2022-10-13 04:13:02 -05:00
| ^^^^ not found in `crate::fluent_generated`
macros: use typed identifiers in subdiag derive As in the diagnostic derive, using typed identifiers in the subdiagnostic derive improves the diagnostics of using the subdiagnostic derive as Fluent messages will be confirmed to exist at compile-time. Signed-off-by: David Wood <david.wood@huawei.com>
2022-06-23 10:12:52 -05:00
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
error[E0425]: cannot find value `__code_29` in this scope
Use `rustc_fluent_macro::fluent_messages!` directly. Currently we always do this: ``` use rustc_fluent_macro::fluent_messages; ... fluent_messages! { "./example.ftl" } ``` But there is no need, we can just do this everywhere: ``` rustc_fluent_macro::fluent_messages! { "./example.ftl" } ``` which is shorter.
2023-11-21 16:53:07 -06:00
--> $DIR/subdiagnostic-derive.rs:714:10
fix and bless ui tests 1/2
2023-04-03 09:36:50 -05:00
|
LL | #[derive(Subdiagnostic)]
| ^^^^^^^^^^^^^ not found in this scope
|
= note: this error originates in the derive macro `Subdiagnostic` (in Nightly builds, run with -Z macro-backtrace for more info)
error: aborting due to 86 previous errors
macros: subdiagnostic derive Add a new derive, `#[derive(SessionSubdiagnostic)]`, which enables deriving structs for labels, notes, helps and suggestions. Signed-off-by: David Wood <david.wood@huawei.com>
2022-04-26 05:59:45 -05:00
Bump syn now that it doesn't affect diagnostics anymore
2023-07-25 07:56:34 -05:00
Some errors have detailed explanations: E0425, E0433.
For more information about an error, try `rustc --explain E0425`.
Reference in New Issue Copy Permalink