rust/tests/ui/rfcs/rfc-2008-non-exhaustive/borrowck-non-exhaustive.stderr

error[E0503]: cannot use `x` because it was mutably borrowed
  --> $DIR/borrowck-non-exhaustive.rs:12:11
   |
LL |     let y = &mut x;
   |             ------ `x` is borrowed here
LL |     match x {
   |           ^ use of borrowed `x`
...
LL |     drop(y);
   |          - borrow later used here

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0503`.
Handle non_exhaustive in borrow checking 2019-11-24 16:39:05 -06:00			error[E0503]: cannot use `x` because it was mutably borrowed
Fix debugger stepping behavior around `match` expressions Previously, we would set up the source lines for `match` expressions so that the code generated to perform the test of the scrutinee was matched to the line of the arm that required the test and then jump from the arm block to the "next" block was matched to all of the lines in the `match` expression. While that makes sense, it has the side effect of causing strange stepping behavior in debuggers. I've changed the source information so that all of the generated tests are sourced to `match {scrutinee}` and the jumps are sourced to the last line of the block they are inside. This resolves the weird stepping behavior in all debuggers and resolves some instances of "ambiguous symbol" errors in WinDbg preventing the user from setting breakpoints at `match` expressions. 2021-07-23 17:55:36 -05:00			`--> $DIR/borrowck-non-exhaustive.rs:12:11`
Handle non_exhaustive in borrow checking 2019-11-24 16:39:05 -06:00			`\|`
			`LL \| let y = &mut x;`
Tweak E0597 CC #99430 2023-01-14 21:06:44 -06:00			\| ------ `x` is borrowed here
Handle non_exhaustive in borrow checking 2019-11-24 16:39:05 -06:00			`LL \| match x {`
Fix debugger stepping behavior around `match` expressions Previously, we would set up the source lines for `match` expressions so that the code generated to perform the test of the scrutinee was matched to the line of the arm that required the test and then jump from the arm block to the "next" block was matched to all of the lines in the `match` expression. While that makes sense, it has the side effect of causing strange stepping behavior in debuggers. I've changed the source information so that all of the generated tests are sourced to `match {scrutinee}` and the jumps are sourced to the last line of the block they are inside. This resolves the weird stepping behavior in all debuggers and resolves some instances of "ambiguous symbol" errors in WinDbg preventing the user from setting breakpoints at `match` expressions. 2021-07-23 17:55:36 -05:00			\| ^ use of borrowed `x`
Handle non_exhaustive in borrow checking 2019-11-24 16:39:05 -06:00			`...`
			`LL \| drop(y);`
			`\| - borrow later used here`

Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Handle non_exhaustive in borrow checking 2019-11-24 16:39:05 -06:00
			For more information about this error, try `rustc --explain E0503`.