mathieu/granite-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
granite-rust/src/test/ui/async-await/issue-68112.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

75 lines
3 KiB
Text
Raw Normal View History

Add test for #68112 (existing output)
2020-03-24 17:23:50 -07:00
error: future cannot be sent between threads safely
--> $DIR/issue-68112.rs:34:5
|
LL | require_send(send_fut);
Improve span label
2020-03-24 18:51:16 -07:00
| ^^^^^^^^^^^^ future created by async block is not `Send`
Add test for #68112 (existing output)
2020-03-24 17:23:50 -07:00
|
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
= help: the trait `Sync` is not implemented for `RefCell<i32>`
Incorporate feedback into diagnostics
2020-04-08 11:54:31 -07:00
note: future is not `Send` as it awaits another future which is not `Send`
Use clearer message when obligation is caused by await expr
2020-04-01 18:53:00 -07:00
--> $DIR/issue-68112.rs:31:17
Add test for #68112 (existing output)
2020-03-24 17:23:50 -07:00
|
LL | let _ = non_send_fut.await;
Print output ty for opaque future ty
2021-11-16 16:16:23 -08:00
| ^^^^^^^^^^^^ await occurs here on type `impl Future<Output = Arc<RefCell<i32>>>`, which is not `Send`
Use note to point at bound introducing requirement
2021-07-31 09:26:55 -07:00
note: required by a bound in `require_send`
--> $DIR/issue-68112.rs:11:25
|
LL | fn require_send(_: impl Send) {}
| ^^^^ required by this bound in `require_send`
Add test for #68112 (existing output)
2020-03-24 17:23:50 -07:00
Don't double-annotate the same Span
2020-04-01 19:04:55 -07:00
error: future cannot be sent between threads safely
--> $DIR/issue-68112.rs:43:5
|
LL | require_send(send_fut);
| ^^^^^^^^^^^^ future created by async block is not `Send`
|
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
= help: the trait `Sync` is not implemented for `RefCell<i32>`
Incorporate feedback into diagnostics
2020-04-08 11:54:31 -07:00
note: future is not `Send` as it awaits another future which is not `Send`
Don't double-annotate the same Span
2020-04-01 19:04:55 -07:00
--> $DIR/issue-68112.rs:40:17
|
LL | let _ = make_non_send_future1().await;
Print output ty for opaque future ty
2021-11-16 16:16:23 -08:00
| ^^^^^^^^^^^^^^^^^^^^^^^ await occurs here on type `impl Future<Output = Arc<RefCell<i32>>>`, which is not `Send`
Use note to point at bound introducing requirement
2021-07-31 09:26:55 -07:00
note: required by a bound in `require_send`
--> $DIR/issue-68112.rs:11:25
|
LL | fn require_send(_: impl Send) {}
| ^^^^ required by this bound in `require_send`
Don't double-annotate the same Span
2020-04-01 19:04:55 -07:00
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
error[E0277]: `RefCell<i32>` cannot be shared between threads safely
Incorporate feedback into diagnostics
2020-04-08 11:54:31 -07:00
--> $DIR/issue-68112.rs:60:5
Add test for #68112 (existing output)
2020-03-24 17:23:50 -07:00
|
LL | require_send(send_fut);
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
| ^^^^^^^^^^^^ `RefCell<i32>` cannot be shared between threads safely
|
= help: the trait `Sync` is not implemented for `RefCell<i32>`
= note: required because of the requirements on the impl of `Send` for `Arc<RefCell<i32>>`
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 async block
--> $DIR/issue-68112.rs:47:31
|
LL | async fn ready2<T>(t: T) -> T { t }
| ^^^^^
note: required because it appears within the type `impl Future<Output = Arc<RefCell<i32>>>`
--> $DIR/issue-68112.rs:48:31
|
LL | fn make_non_send_future2() -> impl Future<Output = Arc<RefCell<i32>>> {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: required because it captures the following types: `ResumeTy`, `impl Future<Output = Arc<RefCell<i32>>>`, `()`, `i32`, `Ready<i32>`
note: required because it's used within this async block
--> $DIR/issue-68112.rs:55:26
|
LL | let send_fut = async {
| __________________________^
LL | | let non_send_fut = make_non_send_future2();
LL | | let _ = non_send_fut.await;
LL | | ready(0).await;
LL | | };
| |_____^
Use note to point at bound introducing requirement
2021-07-31 09:26:55 -07:00
note: required by a bound in `require_send`
--> $DIR/issue-68112.rs:11:25
|
LL | fn require_send(_: impl Send) {}
| ^^^^ required by this bound in `require_send`
Add test for #68112 (existing output)
2020-03-24 17:23:50 -07:00
Don't double-annotate the same Span
2020-04-01 19:04:55 -07:00
error: aborting due to 3 previous errors
Add test for #68112 (existing output)
2020-03-24 17:23:50 -07:00
For more information about this error, try `rustc --explain E0277`.
Reference in a new issue Copy permalink