2019-04-22 02:40:08 -05:00
|
|
|
error[E0501]: cannot borrow `*f` as mutable because previous closure requires unique access
|
|
|
|
|
--> $DIR/borrowck-insert-during-each.rs:16:5
|
2018-08-08 07:28:26 -05:00
|
|
|
|
|
2019-04-22 02:40:08 -05:00
|
|
|
LL | f.foo(
|
|
|
|
|
| ^ --- first borrow later used by call
|
|
|
|
|
| _____|
|
|
|
|
|
| |
|
|
|
|
|
LL | |
|
|
|
|
|
LL | | |a| {
|
|
|
|
|
| | --- closure construction occurs here
|
|
|
|
|
LL | | f.n.insert(*a);
|
2021-03-17 01:51:27 -05:00
|
|
|
| | --- first borrow occurs due to use of `f` in closure
|
2019-04-22 02:40:08 -05:00
|
|
|
LL | | })
|
|
|
|
|
| |__________^ second borrow occurs here
|
|
|
|
|
|
|
|
|
|
error[E0500]: closure requires unique access to `f` but it is already borrowed
|
|
|
|
|
--> $DIR/borrowck-insert-during-each.rs:18:9
|
|
|
|
|
|
|
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
|
|
|
LL | f.foo(
|
|
|
|
|
| - --- first borrow later used by call
|
|
|
|
|
| _____|
|
|
|
|
|
| |
|
|
|
|
|
LL | |
|
|
|
|
|
LL | | |a| {
|
|
|
|
|
| | ^^^ closure construction occurs here
|
|
|
|
|
LL | | f.n.insert(*a);
|
|
|
|
|
| | --- second borrow occurs due to use of `f` in closure
|
|
|
|
|
LL | | })
|
|
|
|
|
| |__________- borrow occurs here
|
2018-08-08 07:28:26 -05:00
|
|
|
|
2019-04-22 02:40:08 -05:00
|
|
|
error: aborting due to 2 previous errors
|
2018-08-08 07:28:26 -05:00
|
|
|
|
2019-04-22 02:40:08 -05:00
|
|
|
Some errors have detailed explanations: E0500, E0501.
|
|
|
|
|
For more information about an error, try `rustc --explain E0500`.
|
