rust/tests/ui/did_you_mean/issue-38147-3.stderr

error[E0596]: cannot borrow `*self.s` as mutable, as it is behind a `&` reference
  --> $DIR/issue-38147-3.rs:7:9
   |
LL |         self.s.push('x');
   |         ^^^^^^^^^^^^^^^^ cannot borrow as mutable
   |
help: consider changing this to be mutable
   |
LL |     s: &'a mut String
   |            +++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0596`.
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			error[E0596]: cannot borrow `*self.s` as mutable, as it is behind a `&` reference
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-38147-3.rs:7:9`
Point to immutable arg/fields when trying to use as &mut Point to immutable borrow arguments and fields when trying to use them as mutable borrows. Add label to primary span on "cannot borrow as mutable" errors. Present the following output when trying to access an immutable borrow's field as mutable: ``` error[E0389]: cannot borrow data mutably in a `&` reference --> $DIR/issue-38147-1.rs:27:9 \| 26 \| fn f(&self) { \| ----- use `&mut self` here to make mutable 27 \| f.s.push('x'); \| ^^^ assignment into an immutable reference ``` And the following when trying to access an immutable struct field as mutable: ``` error: cannot borrow immutable borrowed content `*self.s` as mutable --> $DIR/issue-38147-3.rs:17:9 \| 12 \| s: &'a String \| ------------- use `&'a mut String` here to make mutable ...\| 16 \| fn f(&self) { \| ----- use `&mut self` here to make mutable 17 \| self.s.push('x'); \| ^^^^^^ cannot borrow as mutable ``` 2017-01-17 01:42:11 -06:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| self.s.push('x');`
Use larger span for adjustments on method calls Currently, we use a relatively 'small' span for THIR expressions generated by an 'adjustment' (e.g. an autoderef, autoborrow, unsizing). As a result, if a borrow generated by an adustment ends up causing a borrowcheck error, for example: ```rust let mut my_var = String::new(); let my_ref = &my_var my_var.push('a'); my_ref; ``` then the span for the mutable borrow may end up referring to only the base expression (e.g. `my_var`), rather than the method call which triggered the mutable borrow (e.g. `my_var.push('a')`) Due to a quirk of the MIR borrowck implementation, this doesn't always get exposed in migration mode, but it does in many cases. This commit makes THIR building consistently use 'larger' spans for adjustment expressions The intent of this change it make it clearer to users when it's the specific way in which a variable is used (for example, in a method call) that produdes a borrowcheck error. For example, an error message claiming that a 'mutable borrow occurs here' might be confusing if it just points at a usage of a variable (e.g. `my_var`), when no `&mut` is in sight. Pointing at the entire expression should help to emphasize that the method call itself is responsible for the mutable borrow. In several cases, this makes the `#![feature(nll)]` diagnostic output match up exactly with the default (migration mode) output. As a result, several `.nll.stderr` files end up getting removed entirely. 2021-09-16 15:01:22 -05:00			`\| ^^^^^^^^^^^^^^^^ cannot borrow as mutable`
Improve suggestion to change struct field to &mut 2021-12-04 01:57:31 -06:00			`\|`
			`help: consider changing this to be mutable`
			`\|`
			`LL \| s: &'a mut String`
			`\| +++`
Point to immutable arg/fields when trying to use as &mut Point to immutable borrow arguments and fields when trying to use them as mutable borrows. Add label to primary span on "cannot borrow as mutable" errors. Present the following output when trying to access an immutable borrow's field as mutable: ``` error[E0389]: cannot borrow data mutably in a `&` reference --> $DIR/issue-38147-1.rs:27:9 \| 26 \| fn f(&self) { \| ----- use `&mut self` here to make mutable 27 \| f.s.push('x'); \| ^^^ assignment into an immutable reference ``` And the following when trying to access an immutable struct field as mutable: ``` error: cannot borrow immutable borrowed content `*self.s` as mutable --> $DIR/issue-38147-3.rs:17:9 \| 12 \| s: &'a String \| ------------- use `&'a mut String` here to make mutable ...\| 16 \| fn f(&self) { \| ----- use `&mut self` here to make mutable 17 \| self.s.push('x'); \| ^^^^^^ cannot borrow as mutable ``` 2017-01-17 01:42:11 -06:00
Revert "Change error count messages" This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e. 2017-07-02 05:49:30 -05:00			`error: aborting due to previous error`
Point to immutable arg/fields when trying to use as &mut Point to immutable borrow arguments and fields when trying to use them as mutable borrows. Add label to primary span on "cannot borrow as mutable" errors. Present the following output when trying to access an immutable borrow's field as mutable: ``` error[E0389]: cannot borrow data mutably in a `&` reference --> $DIR/issue-38147-1.rs:27:9 \| 26 \| fn f(&self) { \| ----- use `&mut self` here to make mutable 27 \| f.s.push('x'); \| ^^^ assignment into an immutable reference ``` And the following when trying to access an immutable struct field as mutable: ``` error: cannot borrow immutable borrowed content `*self.s` as mutable --> $DIR/issue-38147-3.rs:17:9 \| 12 \| s: &'a String \| ------------- use `&'a mut String` here to make mutable ...\| 16 \| fn f(&self) { \| ----- use `&mut self` here to make mutable 17 \| self.s.push('x'); \| ^^^^^^ cannot borrow as mutable ``` 2017-01-17 01:42:11 -06:00
update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0596`.