rust/tests/ui/codemap_tests/one_line.stderr

error[E0499]: cannot borrow `v` as mutable more than once at a time
  --> $DIR/one_line.rs:3:12
   |
LL |     v.push(v.pop().unwrap());
   |     - ---- ^ second mutable borrow occurs here
   |     | |
   |     | first borrow later used by call
   |     first mutable borrow occurs here
   |
help: try adding a local storing this argument...
  --> $DIR/one_line.rs:3:12
   |
LL |     v.push(v.pop().unwrap());
   |            ^^^^^^^
help: ...and then using that local as the argument to this call
  --> $DIR/one_line.rs:3:5
   |
LL |     v.push(v.pop().unwrap());
   |     ^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0499`.
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 16:53:42 -05:00			error[E0499]: cannot borrow `v` as mutable more than once at a time
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/one_line.rs:3:12`
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 16:53:42 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| v.push(v.pop().unwrap());`
Do not set up wrong span for adjustments 2023-06-22 15:30:23 -05:00			`\| - ---- ^ second mutable borrow occurs here`
			`\| \| \|`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`\| \| first borrow later used by call`
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 16:53:42 -05:00			`\| first mutable borrow occurs here`
Suggest using a temporary variable to fix borrowck errors In Rust, nesting method calls with both require `&mut` access to `self` produces a borrow-check error: error[E0499]: cannot borrow `*self` as mutable more than once at a time --> src/lib.rs:7:14 \| 7 \| self.foo(self.bar()); \| ---------^^^^^^^^^^- \| \| \| \| \| \| \| second mutable borrow occurs here \| \| first borrow later used by call \| first mutable borrow occurs here That's because Rust has a left-to-right evaluation order, and the method receiver is passed first. Thus, the argument to the method cannot then mutate `self`. There's an easy solution to this error: just extract a local variable for the inner argument: let tmp = self.bar(); self.foo(tmp); However, the error doesn't give any suggestion of how to solve the problem. As a result, new users may assume that it's impossible to express their code correctly and get stuck. This commit adds a (non-structured) suggestion to extract a local variable for the inner argument to solve the error. The suggestion uses heuristics that eliminate most false positives, though there are a few false negatives (cases where the suggestion should be emitted but is not). Those other cases can be implemented in a future change. 2021-03-15 17:09:06 -05:00			`\|`
			`help: try adding a local storing this argument...`
			`--> $DIR/one_line.rs:3:12`
			`\|`
			`LL \| v.push(v.pop().unwrap());`
			`\| ^^^^^^^`
			`help: ...and then using that local as the argument to this call`
			`--> $DIR/one_line.rs:3:5`
			`\|`
			`LL \| v.push(v.pop().unwrap());`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^`
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 16:53:42 -05:00
Revert "Change error count messages" This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e. 2017-07-02 05:49:30 -05:00			`error: aborting due to previous error`
Add fix for tabs. Move error unit tests->ui tests 2016-07-13 16:53:42 -05:00
update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0499`.