rust/tests/ui/issues/issue-53251.stderr

error[E0107]: associated function takes 0 generic arguments but 1 generic argument was supplied
  --> $DIR/issue-53251.rs:11:20
   |
LL |                 S::f::<i64>();
   |                    ^------- help: remove these generics
   |                    |
   |                    expected 0 generic arguments
...
LL | impl_add!(a b);
   | -------------- in this macro invocation
   |
note: associated function defined here, with 0 generic parameters
  --> $DIR/issue-53251.rs:4:8
   |
LL |     fn f() {}
   |        ^
   = note: this error originates in the macro `impl_add` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0107]: associated function takes 0 generic arguments but 1 generic argument was supplied
  --> $DIR/issue-53251.rs:11:20
   |
LL |                 S::f::<i64>();
   |                    ^------- help: remove these generics
   |                    |
   |                    expected 0 generic arguments
...
LL | impl_add!(a b);
   | -------------- in this macro invocation
   |
note: associated function defined here, with 0 generic parameters
  --> $DIR/issue-53251.rs:4:8
   |
LL |     fn f() {}
   |        ^
   = note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
   = note: this error originates in the macro `impl_add` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0107`.
diagnostics: remove inconsistent English article "this" from E0107 Consider `tests/ui/const-generics/generic_const_exprs/issue-102768.stderr`, the error message where it gives additional notes about where the associated type is defined, and how the dead code lint doesn't have an article, like in `tests/ui/lint/dead-code/issue-85255.stderr`. They don't have articles, so it seems unnecessary to have one here. 2023-02-23 17:27:06 +00:00			`error[E0107]: associated function takes 0 generic arguments but 1 generic argument was supplied`
Remove redundant `ignore-tidy-linelength` annotations This is step 2 towards fixing #77548. In the codegen and codegen-units test suites, the `//` comment markers were kept in order not to affect any source locations. This is because these tests cannot be automatically `--bless`ed. 2021-04-03 11:05:11 +00:00			`--> $DIR/issue-53251.rs:11:20`
Mark prior failure to avoid ICE Fix #53251 2018-08-13 22:28:18 +00:00			`\|`
			`LL \| S::f::<i64>();`
Rework diagnostics for wrong number of generic args 2021-01-02 18:45:11 +00:00			`\| ^------- help: remove these generics`
			`\| \|`
improve diagnosts for GATs 2021-02-18 20:01:44 +00:00			`\| expected 0 generic arguments`
Mark prior failure to avoid ICE Fix #53251 2018-08-13 22:28:18 +00:00			`...`
			`LL \| impl_add!(a b);`
Bless tests 2021-10-14 18:28:28 +00:00			`\| -------------- in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 13:56:47 +00:00			`\|`
improve diagnosts for GATs 2021-02-18 20:01:44 +00:00			`note: associated function defined here, with 0 generic parameters`
Remove redundant `ignore-tidy-linelength` annotations This is step 2 towards fixing #77548. In the codegen and codegen-units test suites, the `//` comment markers were kept in order not to affect any source locations. This is because these tests cannot be automatically `--bless`ed. 2021-04-03 11:05:11 +00:00			`--> $DIR/issue-53251.rs:4:8`
Rework diagnostics for wrong number of generic args 2021-01-02 18:45:11 +00:00			`\|`
			`LL \| fn f() {}`
			`\| ^`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 19:52:25 +00:00			= note: this error originates in the macro `impl_add` (in Nightly builds, run with -Z macro-backtrace for more info)
Mark prior failure to avoid ICE Fix #53251 2018-08-13 22:28:18 +00:00
diagnostics: remove inconsistent English article "this" from E0107 Consider `tests/ui/const-generics/generic_const_exprs/issue-102768.stderr`, the error message where it gives additional notes about where the associated type is defined, and how the dead code lint doesn't have an article, like in `tests/ui/lint/dead-code/issue-85255.stderr`. They don't have articles, so it seems unnecessary to have one here. 2023-02-23 17:27:06 +00:00			`error[E0107]: associated function takes 0 generic arguments but 1 generic argument was supplied`
Remove redundant `ignore-tidy-linelength` annotations This is step 2 towards fixing #77548. In the codegen and codegen-units test suites, the `//` comment markers were kept in order not to affect any source locations. This is because these tests cannot be automatically `--bless`ed. 2021-04-03 11:05:11 +00:00			`--> $DIR/issue-53251.rs:11:20`
Update tests 2020-01-08 17:02:10 +00:00			`\|`
			`LL \| S::f::<i64>();`
Rework diagnostics for wrong number of generic args 2021-01-02 18:45:11 +00:00			`\| ^------- help: remove these generics`
			`\| \|`
improve diagnosts for GATs 2021-02-18 20:01:44 +00:00			`\| expected 0 generic arguments`
Update tests 2020-01-08 17:02:10 +00:00			`...`
			`LL \| impl_add!(a b);`
Bless tests 2021-10-14 18:28:28 +00:00			`\| -------------- in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 13:56:47 +00:00			`\|`
improve diagnosts for GATs 2021-02-18 20:01:44 +00:00			`note: associated function defined here, with 0 generic parameters`
Remove redundant `ignore-tidy-linelength` annotations This is step 2 towards fixing #77548. In the codegen and codegen-units test suites, the `//` comment markers were kept in order not to affect any source locations. This is because these tests cannot be automatically `--bless`ed. 2021-04-03 11:05:11 +00:00			`--> $DIR/issue-53251.rs:4:8`
Rework diagnostics for wrong number of generic args 2021-01-02 18:45:11 +00:00			`\|`
			`LL \| fn f() {}`
			`\| ^`
Add a note to duplicate diagnostics 2023-10-04 18:34:50 +00:00			= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 19:52:25 +00:00			= note: this error originates in the macro `impl_add` (in Nightly builds, run with -Z macro-backtrace for more info)
Update tests 2020-01-08 17:02:10 +00:00
			`error: aborting due to 2 previous errors`
Mark prior failure to avoid ICE Fix #53251 2018-08-13 22:28:18 +00:00
updates tests to use new error code 2018-08-22 01:12:23 +00:00			For more information about this error, try `rustc --explain E0107`.