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

error[E0499]: cannot borrow `*bar` as mutable more than once at a time
  --> $DIR/issue-51117.rs:10:13
   |
LL |         Some(baz) => {
   |              --- first mutable borrow occurs here
LL |             bar.take();
   |             ^^^^^^^^^^ second mutable borrow occurs here
LL |             drop(baz);
   |                  --- first borrow later used here

error: aborting due to previous error

For more information about this error, try `rustc --explain E0499`.
change `PointerKind::Implicit` to a note `PointerKind` is included in `LoanPath` and hence forms part of the equality check; this led to having two unequal paths that both represent `x`, depending on whether the `` was inserted automatically or explicitly. Bad mojo. The `note` field, in contrast, is intended more-or-less primarily for this purpose of adding extra data. 2018-05-31 09:17:51 -05:00			error[E0499]: cannot borrow `*bar` as mutable more than once at a time
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-51117.rs:10:13`
change `PointerKind::Implicit` to a note `PointerKind` is included in `LoanPath` and hence forms part of the equality check; this led to having two unequal paths that both represent `x`, depending on whether the `` was inserted automatically or explicitly. Bad mojo. The `note` field, in contrast, is intended more-or-less primarily for this purpose of adding extra data. 2018-05-31 09:17:51 -05:00			`\|`
			`LL \| Some(baz) => {`
			`\| --- first mutable borrow occurs here`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| bar.take();`
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			`\| ^^^^^^^^^^ second mutable borrow occurs here`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`LL \| drop(baz);`
			`\| --- first borrow later used here`
change `PointerKind::Implicit` to a note `PointerKind` is included in `LoanPath` and hence forms part of the equality check; this led to having two unequal paths that both represent `x`, depending on whether the `` was inserted automatically or explicitly. Bad mojo. The `note` field, in contrast, is intended more-or-less primarily for this purpose of adding extra data. 2018-05-31 09:17:51 -05:00
			`error: aborting due to previous error`

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