rust/tests/ui/async-await/issues/issue-61187.stderr

error[E0596]: cannot borrow `data` as mutable, as it is not declared as mutable
  --> $DIR/issue-61187.rs:6:5
   |
LL |     data.reverse();
   |     ^^^^^^^^^^^^^^ cannot borrow as mutable
   |
help: consider changing this to be mutable
   |
LL | async fn response(mut data: Vec<u8>) {
   |                   +++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0596`.
rustc: async fn drop order lowering in HIR This commit re-implements the async fn drop order lowering changes so that it all takes place in HIR lowering, building atop the work done by `@eddyb` to refactor `Res::Upvar`. Previously, this types involved in the lowering were constructed in libsyntax as they had to be used during name resolution and HIR lowering. This was awful because none of that logic should have existed in libsyntax. This commit also changes `ArgSource` to keep a `HirId` to the original argument pattern rather than a cloned copy of the pattern. 2019-05-29 11:28:51 -05:00			error[E0596]: cannot borrow `data` as mutable, as it is not declared as mutable
--bless post no async_await gates in tests. 2019-08-01 20:48:43 -05:00			`--> $DIR/issue-61187.rs:6:5`
rustc: async fn drop order lowering in HIR This commit re-implements the async fn drop order lowering changes so that it all takes place in HIR lowering, building atop the work done by `@eddyb` to refactor `Res::Upvar`. Previously, this types involved in the lowering were constructed in libsyntax as they had to be used during name resolution and HIR lowering. This was awful because none of that logic should have existed in libsyntax. This commit also changes `ArgSource` to keep a `HirId` to the original argument pattern rather than a cloned copy of the pattern. 2019-05-29 11:28:51 -05:00			`\|`
			`LL \| data.reverse();`
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`
Verbose suggestions 2023-01-01 02:06:31 -06:00			`\|`
			`help: consider changing this to be mutable`
			`\|`
			`LL \| async fn response(mut data: Vec<u8>) {`
			`\| +++`
rustc: async fn drop order lowering in HIR This commit re-implements the async fn drop order lowering changes so that it all takes place in HIR lowering, building atop the work done by `@eddyb` to refactor `Res::Upvar`. Previously, this types involved in the lowering were constructed in libsyntax as they had to be used during name resolution and HIR lowering. This was awful because none of that logic should have existed in libsyntax. This commit also changes `ArgSource` to keep a `HirId` to the original argument pattern rather than a cloned copy of the pattern. 2019-05-29 11:28:51 -05:00
			`error: aborting due to previous error`

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