rust/tests/ui/no-send-res-ports.stderr

error[E0277]: `Rc<()>` cannot be sent between threads safely
  --> $DIR/no-send-res-ports.rs:25:19
   |
LL |       thread::spawn(move|| {
   |       ------------- ^-----
   |       |             |
   |  _____|_____________within this `{closure@$DIR/no-send-res-ports.rs:25:19: 25:25}`
   | |     |
   | |     required by a bound introduced by this call
LL | |
LL | |         let y = x;
LL | |         println!("{:?}", y);
LL | |     });
   | |_____^ `Rc<()>` cannot be sent between threads safely
   |
   = help: within `{closure@$DIR/no-send-res-ports.rs:25:19: 25:25}`, the trait `Send` is not implemented for `Rc<()>`, which is required by `{closure@$DIR/no-send-res-ports.rs:25:19: 25:25}: Send`
note: required because it appears within the type `Port<()>`
  --> $DIR/no-send-res-ports.rs:5:8
   |
LL | struct Port<T>(Rc<T>);
   |        ^^^^
note: required because it appears within the type `Foo`
  --> $DIR/no-send-res-ports.rs:9:12
   |
LL |     struct Foo {
   |            ^^^
note: required because it's used within this closure
  --> $DIR/no-send-res-ports.rs:25:19
   |
LL |     thread::spawn(move|| {
   |                   ^^^^^^
note: required by a bound in `spawn`
  --> $SRC_DIR/std/src/thread/mod.rs:LL:COL

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
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 02:40:56 -05:00			error[E0277]: `Rc<()>` cannot be sent between threads safely
Rework point-at-arg 2022-08-16 01:27:22 -05:00			`--> $DIR/no-send-res-ports.rs:25:19`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Rework point-at-arg 2022-08-16 01:27:22 -05:00			`LL \| thread::spawn(move\|\| {`
			`\| ------------- ^-----`
			`\| \| \|`
adjust how closure/generator types and rvalues are printed 2023-09-09 01:36:50 -05:00			\| _____\|_____________within this `{closure@$DIR/no-send-res-ports.rs:25:19: 25:25}`
Rework point-at-arg 2022-08-16 01:27:22 -05:00			`\| \| \|`
			`\| \| required by a bound introduced by this call`
			`LL \| \|`
			`LL \| \| let y = x;`
			`LL \| \| println!("{:?}", y);`
			`LL \| \| });`
			\| \|_____^ `Rc<()>` cannot be sent between threads safely
Remove trailing whitespace from error messages 2021-06-10 06:52:00 -05: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 12:31:02 -06:00			= help: within `{closure@$DIR/no-send-res-ports.rs:25:19: 25:25}`, the trait `Send` is not implemented for `Rc<()>`, which is required by `{closure@$DIR/no-send-res-ports.rs:25:19: 25:25}: Send`
Point at `impl` and type defs introducing requirements on E0277 2021-03-30 15:37:30 -05:00			note: required because it appears within the type `Port<()>`
			`--> $DIR/no-send-res-ports.rs:5:8`
			`\|`
			`LL \| struct Port<T>(Rc<T>);`
			`\| ^^^^`
			note: required because it appears within the type `Foo`
			`--> $DIR/no-send-res-ports.rs:9:12`
			`\|`
			`LL \| struct Foo {`
			`\| ^^^`
Greatly improve error reporting for futures and generators in `note_obligation_cause_code` Most futures don't go through this code path, because they're caught by `maybe_note_obligation_cause_for_async_await`. But all generators do, and `maybe_note` is imperfect and doesn't catch all futures. Improve the error message for those it misses. At some point, we may want to consider unifying this with the code for `maybe_note_async_await`, so that `async_await` notes all parent constraints, and `note_obligation` can point to yield points. But both functions are quite complicated, and it's not clear to me how to combine them; this seems like a good incremental improvement. 2022-06-19 13:59:36 -05:00			`note: required because it's used within this closure`
			`--> $DIR/no-send-res-ports.rs:25:19`
			`\|`
Shorten span for closures. 2022-06-27 00:45:35 -05:00			`LL \| thread::spawn(move\|\| {`
			`\| ^^^^^^`
Use note to point at bound introducing requirement 2021-07-31 11:26:55 -05:00			note: required by a bound in `spawn`
			`--> $SRC_DIR/std/src/thread/mod.rs:LL:COL`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
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`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			For more information about this error, try `rustc --explain E0277`.