nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-23 23:34:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
68c2f5ba0f
rust/tests/ui/proc-macro/amputate-span.stderr

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

26 lines
660 B
Plaintext
Raw Normal View History

Adjusted diagnostic output so that if there is no `use` in a item sequence, then we just suggest the first legal position where you could inject a use. To do this, I added `inject_use_span` field to `ModSpans`, and populate it in parser (it is the span of the first token found after inner attributes, if any). Then I rewrote the use-suggestion code to utilize it, and threw out some stuff that is now unnecessary with this in place. (I think the result is easier to understand.) Then I added a test of issue 87613.
2022-01-20 19:07:54 +00:00
error[E0433]: failed to resolve: use of undeclared type `Command`
run rust-fix in amputate-span.rs. (Thanks to ekuber for pushing me to do this.)
2022-03-11 21:57:34 +00:00
--> $DIR/amputate-span.rs:49:5
Adjusted diagnostic output so that if there is no `use` in a item sequence, then we just suggest the first legal position where you could inject a use. To do this, I added `inject_use_span` field to `ModSpans`, and populate it in parser (it is the span of the first token found after inner attributes, if any). Then I rewrote the use-suggestion code to utilize it, and threw out some stuff that is now unnecessary with this in place. (I think the result is easier to understand.) Then I added a test of issue 87613.
2022-01-20 19:07:54 +00:00
|
LL | Command::new("git");
Correct inconsistent error messages in tests
2022-10-27 06:36:07 +00:00
| ^^^^^^^ use of undeclared type `Command`
Adjusted diagnostic output so that if there is no `use` in a item sequence, then we just suggest the first legal position where you could inject a use. To do this, I added `inject_use_span` field to `ModSpans`, and populate it in parser (it is the span of the first token found after inner attributes, if any). Then I rewrote the use-suggestion code to utilize it, and threw out some stuff that is now unnecessary with this in place. (I think the result is easier to understand.) Then I added a test of issue 87613.
2022-01-20 19:07:54 +00:00
|
help: consider importing this struct
|
Tweak output for 'add line' suggestion
2023-03-18 02:18:39 +00:00
LL + use std::process::Command;
Adjusted diagnostic output so that if there is no `use` in a item sequence, then we just suggest the first legal position where you could inject a use. To do this, I added `inject_use_span` field to `ModSpans`, and populate it in parser (it is the span of the first token found after inner attributes, if any). Then I rewrote the use-suggestion code to utilize it, and threw out some stuff that is now unnecessary with this in place. (I think the result is easier to understand.) Then I added a test of issue 87613.
2022-01-20 19:07:54 +00:00
|
error[E0433]: failed to resolve: use of undeclared type `Command`
run rust-fix in amputate-span.rs. (Thanks to ekuber for pushing me to do this.)
2022-03-11 21:57:34 +00:00
--> $DIR/amputate-span.rs:63:9
Adjusted diagnostic output so that if there is no `use` in a item sequence, then we just suggest the first legal position where you could inject a use. To do this, I added `inject_use_span` field to `ModSpans`, and populate it in parser (it is the span of the first token found after inner attributes, if any). Then I rewrote the use-suggestion code to utilize it, and threw out some stuff that is now unnecessary with this in place. (I think the result is easier to understand.) Then I added a test of issue 87613.
2022-01-20 19:07:54 +00:00
|
LL | Command::new("git");
Correct inconsistent error messages in tests
2022-10-27 06:36:07 +00:00
| ^^^^^^^ use of undeclared type `Command`
Adjusted diagnostic output so that if there is no `use` in a item sequence, then we just suggest the first legal position where you could inject a use. To do this, I added `inject_use_span` field to `ModSpans`, and populate it in parser (it is the span of the first token found after inner attributes, if any). Then I rewrote the use-suggestion code to utilize it, and threw out some stuff that is now unnecessary with this in place. (I think the result is easier to understand.) Then I added a test of issue 87613.
2022-01-20 19:07:54 +00:00
|
help: consider importing this struct
|
Tweak output for 'add line' suggestion
2023-03-18 02:18:39 +00:00
LL + use std::process::Command;
Adjusted diagnostic output so that if there is no `use` in a item sequence, then we just suggest the first legal position where you could inject a use. To do this, I added `inject_use_span` field to `ModSpans`, and populate it in parser (it is the span of the first token found after inner attributes, if any). Then I rewrote the use-suggestion code to utilize it, and threw out some stuff that is now unnecessary with this in place. (I think the result is easier to understand.) Then I added a test of issue 87613.
2022-01-20 19:07:54 +00:00
|
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0433`.
Reference in New Issue Copy Permalink