os-rust/tests/ui/async-await/issue-71137.stderr

error: future cannot be sent between threads safely
  --> $DIR/issue-71137.rs:22:14
   |
LL |   fake_spawn(wrong_mutex());
   |              ^^^^^^^^^^^^^ future returned by `wrong_mutex` is not `Send`
   |
   = help: within `impl Future<Output = ()>`, the trait `Send` is not implemented for `MutexGuard<'_, i32>`, which is required by `impl Future<Output = ()>: Send`
note: future is not `Send` as this value is used across an await
  --> $DIR/issue-71137.rs:14:26
   |
LL |     let mut guard = m.lock().unwrap();
   |         --------- has type `MutexGuard<'_, i32>` which is not `Send`
LL |     (async { "right"; }).await;
   |                          ^^^^^ await occurs here, with `mut guard` maybe used later
note: required by a bound in `fake_spawn`
  --> $DIR/issue-71137.rs:8:27
   |
LL | fn fake_spawn<F: Future + Send + 'static>(f: F) { }
   |                           ^^^^ required by this bound in `fake_spawn`

error: aborting due to 1 previous error
add test for correct await span 2020-04-16 23:14:11 +08:00			`error: future cannot be sent between threads safely`
Feature gate and make must_not_suspend allow-by-default This lint is not yet ready for stable use, primarily due to false positives in edge cases; we want to test it out more before stabilizing. 2021-10-12 09:10:05 -07:00			`--> $DIR/issue-71137.rs:22:14`
add test for correct await span 2020-04-16 23:14:11 +08:00			`\|`
			`LL \| fake_spawn(wrong_mutex());`
fix(rustc_typeck): report function argument errors on matching type Fixes #90101 2021-10-22 13:49:12 -07:00			\| ^^^^^^^^^^^^^ future returned by `wrong_mutex` is not `Send`
add test for correct await span 2020-04-16 23:14:11 +08:00			`\|`
Provide more context on derived obligation error primary label Expand the primary span of E0277 when the immediate unmet bound is not what the user wrote: ``` error[E0277]: the trait bound `i32: Bar` is not satisfied --> f100.rs:6:6 \| 6 \| <i32 as Foo>::foo(); \| ^^^ the trait `Bar` is not implemented for `i32`, which is required by `i32: Foo` \| help: this trait has no implementations, consider adding one --> f100.rs:2:1 \| 2 \| trait Bar {} \| ^^^^^^^^^ note: required for `i32` to implement `Foo` --> f100.rs:3:14 \| 3 \| impl<T: Bar> Foo for T {} \| --- ^^^ ^ \| \| \| unsatisfied trait bound introduced here ``` Fix #40120. 2024-01-29 18:31:02 +00:00			= help: within `impl Future<Output = ()>`, the trait `Send` is not implemented for `MutexGuard<'_, i32>`, which is required by `impl Future<Output = ()>: Send`
add test for correct await span 2020-04-16 23:14:11 +08:00			note: future is not `Send` as this value is used across an await
Tweak await span 2023-04-25 18:59:16 +00:00			`--> $DIR/issue-71137.rs:14:26`
add test for correct await span 2020-04-16 23:14:11 +08:00			`\|`
			`LL \| let mut guard = m.lock().unwrap();`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			\| --------- has type `MutexGuard<'_, i32>` which is not `Send`
add test for correct await span 2020-04-16 23:14:11 +08:00			`LL \| (async { "right"; }).await;`
Tweak await span 2023-04-25 18:59:16 +00:00			\| ^^^^^ await occurs here, with `mut guard` maybe used later
Use note to point at bound introducing requirement 2021-07-31 09:26:55 -07:00			note: required by a bound in `fake_spawn`
Feature gate and make must_not_suspend allow-by-default This lint is not yet ready for stable use, primarily due to false positives in edge cases; we want to test it out more before stabilizing. 2021-10-12 09:10:05 -07:00			`--> $DIR/issue-71137.rs:8:27`
Use note to point at bound introducing requirement 2021-07-31 09:26:55 -07:00			`\|`
			`LL \| fn fake_spawn<F: Future + Send + 'static>(f: F) { }`
			\| ^^^^ required by this bound in `fake_spawn`
add test for correct await span 2020-04-16 23:14:11 +08:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
add test for correct await span 2020-04-16 23:14:11 +08:00