rust/tests/ui/hygiene/missing-self-diag.stderr

error[E0424]: expected value, found module `self`
  --> $DIR/missing-self-diag.rs:10:9
   |
LL |           self.bar();
   |           ^^^^ `self` value is a keyword only available in methods with a `self` parameter
...
LL | /     pub fn foo(&self) {
LL | |         call_bar!();
   | |         ----------- in this macro invocation
LL | |     }
   | |_____- this function has a `self` parameter, but a macro invocation can only access identifiers it receives from parameters
   |
   = note: this error originates in the macro `call_bar` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error

For more information about this error, try `rustc --explain E0424`.
Emit a better diagnostic when function actually has a 'self' parameter Fixes #66898 When we are unable to resolve a reference to `self`, we current assume that the containing function doesn't have a `self` parameter, and emit an error message accordingly. However, if the reference to `self` was created by a macro invocation, then resolution will correctly fail, due to hygiene. In this case, we don't want to tell the user that the containing fuction doesn't have a 'self' paramter if it actually has one. This PR checks for the precense of a 'self' parameter, and adjusts the error message we emit accordingly. TODO: The exact error message we emit could probably be improved. Should we explicitly mention hygiene? 2020-05-17 17:28:12 -05:00			error[E0424]: expected value, found module `self`
			`--> $DIR/missing-self-diag.rs:10:9`
			`\|`
			`LL \| self.bar();`
			\| ^^^^ `self` value is a keyword only available in methods with a `self` parameter
			`...`
			`LL \| / pub fn foo(&self) {`
			`LL \| \| call_bar!();`
Bless tests 2021-10-14 13:28:28 -05:00			`\| \| ----------- in this macro invocation`
Emit a better diagnostic when function actually has a 'self' parameter Fixes #66898 When we are unable to resolve a reference to `self`, we current assume that the containing function doesn't have a `self` parameter, and emit an error message accordingly. However, if the reference to `self` was created by a macro invocation, then resolution will correctly fail, due to hygiene. In this case, we don't want to tell the user that the containing fuction doesn't have a 'self' paramter if it actually has one. This PR checks for the precense of a 'self' parameter, and adjusts the error message we emit accordingly. TODO: The exact error message we emit could probably be improved. Should we explicitly mention hygiene? 2020-05-17 17:28:12 -05:00			`LL \| \| }`
			\| \|_____- this function has a `self` parameter, but a macro invocation can only access identifiers it receives from parameters
			`\|`
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 13:52:25 -06:00			= note: this error originates in the macro `call_bar` (in Nightly builds, run with -Z macro-backtrace for more info)
Emit a better diagnostic when function actually has a 'self' parameter Fixes #66898 When we are unable to resolve a reference to `self`, we current assume that the containing function doesn't have a `self` parameter, and emit an error message accordingly. However, if the reference to `self` was created by a macro invocation, then resolution will correctly fail, due to hygiene. In this case, we don't want to tell the user that the containing fuction doesn't have a 'self' paramter if it actually has one. This PR checks for the precense of a 'self' parameter, and adjusts the error message we emit accordingly. TODO: The exact error message we emit could probably be improved. Should we explicitly mention hygiene? 2020-05-17 17:28:12 -05:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0424`.