mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
50603cbb6d
rust/tests/ui-fulldeps/session-diagnostic/diagnostic-derive-doc-comment-field.stderr

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

32 lines
1.3 KiB
Plaintext
Raw Normal View History

Rename `IntoDiagnosticArg` as `IntoDiagArg`. Also rename `into_diagnostic_arg` as `into_diag_arg`, and `NotIntoDiagnosticArg` as `NotInotDiagArg`.
2024-03-04 23:53:24 -06:00
error[E0277]: the trait bound `NotIntoDiagArg: IntoDiagArg` is not satisfied
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/diagnostic-derive-doc-comment-field.rs:36:10
Diagnostic args are still args if they're documented
2023-05-03 18:22:57 -05:00
|
LL | #[derive(Diagnostic)]
Make spans a bit better
2023-05-03 18:53:44 -05:00
| ---------- required by a bound introduced by this call
...
Rename `IntoDiagnosticArg` as `IntoDiagArg`. Also rename `into_diagnostic_arg` as `into_diag_arg`, and `NotIntoDiagnosticArg` as `NotInotDiagArg`.
2024-03-04 23:53:24 -06:00
LL | arg: NotIntoDiagArg,
| ^^^^^^^^^^^^^^ the trait `IntoDiagArg` is not implemented for `NotIntoDiagArg`
Diagnostic args are still args if they're documented
2023-05-03 18:22:57 -05:00
|
Make spans a bit better
2023-05-03 18:53:44 -05:00
= help: normalized in stderr
Rename `DiagnosticBuilder` as `Diag`. Much better! Note that this involves renaming (and updating the value of) `DIAGNOSTIC_BUILDER` in clippy.
2024-02-22 17:20:45 -06:00
note: required by a bound in `Diag::<'a, G>::arg`
Reduce capabilities of `Diagnostic`. Currently many diagnostic modifier methods are available on both `Diagnostic` and `DiagnosticBuilder`. This commit removes most of them from `Diagnostic`. To minimize the diff size, it keeps them within `diagnostic.rs` but changes the surrounding `impl Diagnostic` block to `impl DiagnosticBuilder`. (I intend to move things around later, to give a more sensible code layout.) `Diagnostic` keeps a few methods that it still needs, like `sub`, `arg`, and `replace_args`. The `forward!` macro, which defined two additional methods per call (e.g. `note` and `with_note`), is replaced by the `with_fn!` macro, which defines one additional method per call (e.g. `with_note`). It's now also only used when necessary -- not all modifier methods currently need a `with_*` form. (New ones can be easily added as necessary.) All this also requires changing `trait AddToDiagnostic` so its methods take `DiagnosticBuilder` instead of `Diagnostic`, which leads to many mechanical changes. `SubdiagnosticMessageOp` gains a type parameter `G`. There are three subdiagnostics -- `DelayedAtWithoutNewline`, `DelayedAtWithNewline`, and `InvalidFlushedDelayedDiagnosticLevel` -- that are created within the diagnostics machinery and appended to external diagnostics. These are handled at the `Diagnostic` level, which means it's now hard to construct them via `derive(Diagnostic)`, so instead we construct them by hand. This has no effect on what they look like when printed. There are lots of new `allow` markers for `untranslatable_diagnostics` and `diagnostics_outside_of_impl`. This is because `#[rustc_lint_diagnostics]` annotations were present on the `Diagnostic` modifier methods, but missing from the `DiagnosticBuilder` modifier methods. They're now present.
2024-02-05 23:44:30 -06:00
--> $COMPILER_DIR/rustc_errors/src/diagnostic.rs:LL:CC
= note: this error originates in the macro `with_fn` (in Nightly builds, run with -Z macro-backtrace for more info)
Diagnostic args are still args if they're documented
2023-05-03 18:22:57 -05:00
Rename `IntoDiagnosticArg` as `IntoDiagArg`. Also rename `into_diagnostic_arg` as `into_diag_arg`, and `NotIntoDiagnosticArg` as `NotInotDiagArg`.
2024-03-04 23:53:24 -06:00
error[E0277]: the trait bound `NotIntoDiagArg: IntoDiagArg` is not satisfied
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/diagnostic-derive-doc-comment-field.rs:46:10
Diagnostic args are still args if they're documented
2023-05-03 18:22:57 -05:00
|
LL | #[derive(Subdiagnostic)]
Make spans a bit better
2023-05-03 18:53:44 -05:00
| ------------- required by a bound introduced by this call
...
Rename `IntoDiagnosticArg` as `IntoDiagArg`. Also rename `into_diagnostic_arg` as `into_diag_arg`, and `NotIntoDiagnosticArg` as `NotInotDiagArg`.
2024-03-04 23:53:24 -06:00
LL | arg: NotIntoDiagArg,
| ^^^^^^^^^^^^^^ the trait `IntoDiagArg` is not implemented for `NotIntoDiagArg`
Diagnostic args are still args if they're documented
2023-05-03 18:22:57 -05:00
|
Make spans a bit better
2023-05-03 18:53:44 -05:00
= help: normalized in stderr
Rename `DiagnosticBuilder` as `Diag`. Much better! Note that this involves renaming (and updating the value of) `DIAGNOSTIC_BUILDER` in clippy.
2024-02-22 17:20:45 -06:00
note: required by a bound in `Diag::<'a, G>::arg`
hide rustc line numbers in test
2023-09-22 03:37:05 -05:00
--> $COMPILER_DIR/rustc_errors/src/diagnostic.rs:LL:CC
Reduce capabilities of `Diagnostic`. Currently many diagnostic modifier methods are available on both `Diagnostic` and `DiagnosticBuilder`. This commit removes most of them from `Diagnostic`. To minimize the diff size, it keeps them within `diagnostic.rs` but changes the surrounding `impl Diagnostic` block to `impl DiagnosticBuilder`. (I intend to move things around later, to give a more sensible code layout.) `Diagnostic` keeps a few methods that it still needs, like `sub`, `arg`, and `replace_args`. The `forward!` macro, which defined two additional methods per call (e.g. `note` and `with_note`), is replaced by the `with_fn!` macro, which defines one additional method per call (e.g. `with_note`). It's now also only used when necessary -- not all modifier methods currently need a `with_*` form. (New ones can be easily added as necessary.) All this also requires changing `trait AddToDiagnostic` so its methods take `DiagnosticBuilder` instead of `Diagnostic`, which leads to many mechanical changes. `SubdiagnosticMessageOp` gains a type parameter `G`. There are three subdiagnostics -- `DelayedAtWithoutNewline`, `DelayedAtWithNewline`, and `InvalidFlushedDelayedDiagnosticLevel` -- that are created within the diagnostics machinery and appended to external diagnostics. These are handled at the `Diagnostic` level, which means it's now hard to construct them via `derive(Diagnostic)`, so instead we construct them by hand. This has no effect on what they look like when printed. There are lots of new `allow` markers for `untranslatable_diagnostics` and `diagnostics_outside_of_impl`. This is because `#[rustc_lint_diagnostics]` annotations were present on the `Diagnostic` modifier methods, but missing from the `DiagnosticBuilder` modifier methods. They're now present.
2024-02-05 23:44:30 -06:00
= note: this error originates in the macro `with_fn` (in Nightly builds, run with -Z macro-backtrace for more info)
Diagnostic args are still args if they're documented
2023-05-03 18:22:57 -05:00
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink