rust/tests/ui/borrowck/issue-93093.stderr

error[E0594]: cannot assign to `self.foo`, which is behind a `&` reference
  --> $DIR/issue-93093.rs:8:9
   |
LL |         self.foo += 1;
   |         ^^^^^^^^^^^^^ `self` is a `&` reference, so the data it refers to cannot be written
   |
help: consider changing this to be a mutable reference
   |
LL |     async fn bar(&mut self) {
   |                  ~~~~~~~~~

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0594`.
[borrowck] Fix help on mutating &self in async fns Previously, when rustc was provided an async function that tried to mutate through a shared reference to an implicit self (as shown in the ui test), rustc would suggest modifying the parameter signature to `&mut` + the fully qualified name of the ty (in the case of the repro `S`). If a user modified their code to match the suggestion, the compiler would not accept it. This commit modifies the suggestion so that when rustc is provided the ui test that is also attached in this commit, it suggests (correctly) `&mut self`. We try to be careful about distinguishing between implicit and explicit self annotations, since the latter seem to be handled correctly already. Fixes rust-lang/rust#93093 2022-01-22 17:35:09 -06:00			error[E0594]: cannot assign to `self.foo`, which is behind a `&` reference
			`--> $DIR/issue-93093.rs:8:9`
			`\|`
			`LL \| self.foo += 1;`
			\| ^^^^^^^^^^^^^ `self` is a `&` reference, so the data it refers to cannot be written
Use verbose suggestions for mutability errors 2022-12-28 23:52:57 -06:00			`\|`
			`help: consider changing this to be a mutable reference`
			`\|`
			`LL \| async fn bar(&mut self) {`
			`\| ~~~~~~~~~`
[borrowck] Fix help on mutating &self in async fns Previously, when rustc was provided an async function that tried to mutate through a shared reference to an implicit self (as shown in the ui test), rustc would suggest modifying the parameter signature to `&mut` + the fully qualified name of the ty (in the case of the repro `S`). If a user modified their code to match the suggestion, the compiler would not accept it. This commit modifies the suggestion so that when rustc is provided the ui test that is also attached in this commit, it suggests (correctly) `&mut self`. We try to be careful about distinguishing between implicit and explicit self annotations, since the latter seem to be handled correctly already. Fixes rust-lang/rust#93093 2022-01-22 17:35:09 -06:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
[borrowck] Fix help on mutating &self in async fns Previously, when rustc was provided an async function that tried to mutate through a shared reference to an implicit self (as shown in the ui test), rustc would suggest modifying the parameter signature to `&mut` + the fully qualified name of the ty (in the case of the repro `S`). If a user modified their code to match the suggestion, the compiler would not accept it. This commit modifies the suggestion so that when rustc is provided the ui test that is also attached in this commit, it suggests (correctly) `&mut self`. We try to be careful about distinguishing between implicit and explicit self annotations, since the latter seem to be handled correctly already. Fixes rust-lang/rust#93093 2022-01-22 17:35:09 -06:00
			For more information about this error, try `rustc --explain E0594`.