rust/tests/ui/kindck/kindck-nonsendable-1.stderr

error[E0277]: `Rc<usize>` cannot be sent between threads safely
  --> $DIR/kindck-nonsendable-1.rs:9:9
   |
LL |     bar(move|| foo(x));
   |     --- ------^^^^^^^
   |     |   |
   |     |   `Rc<usize>` cannot be sent between threads safely
   |     |   within this `[closure@$DIR/kindck-nonsendable-1.rs:9:9: 9:15]`
   |     required by a bound introduced by this call
   |
   = help: within `[closure@$DIR/kindck-nonsendable-1.rs:9:9: 9:15]`, the trait `Send` is not implemented for `Rc<usize>`
note: required because it's used within this closure
  --> $DIR/kindck-nonsendable-1.rs:9:9
   |
LL |     bar(move|| foo(x));
   |         ^^^^^^
note: required by a bound in `bar`
  --> $DIR/kindck-nonsendable-1.rs:5:21
   |
LL | fn bar<F:FnOnce() + Send>(_: F) { }
   |                     ^^^^ required by this bound in `bar`

error: aborting due to 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<usize>` cannot be sent between threads safely
Rework point-at-arg 2022-08-16 01:27:22 -05:00			`--> $DIR/kindck-nonsendable-1.rs:9:9`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
			`LL \| bar(move\|\| foo(x));`
Rework point-at-arg 2022-08-16 01:27:22 -05:00			`\| --- ------^^^^^^^`
			`\| \| \|`
			\| \| `Rc<usize>` cannot be sent between threads safely
			\| \| within this `[closure@$DIR/kindck-nonsendable-1.rs:9:9: 9:15]`
			`\| required by a bound introduced by this call`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Shorten span for closures. 2022-06-27 00:45:35 -05:00			= help: within `[closure@$DIR/kindck-nonsendable-1.rs:9:9: 9:15]`, the trait `Send` is not implemented for `Rc<usize>`
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/kindck-nonsendable-1.rs:9:9`
			`\|`
			`LL \| bar(move\|\| foo(x));`
Shorten span for closures. 2022-06-27 00:45:35 -05:00			`\| ^^^^^^`
Use note to point at bound introducing requirement 2021-07-31 11:26:55 -05:00			note: required by a bound in `bar`
			`--> $DIR/kindck-nonsendable-1.rs:5:21`
			`\|`
			`LL \| fn bar<F:FnOnce() + Send>(_: F) { }`
			\| ^^^^ required by this bound in `bar`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`

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