mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
aae331d610
rust/tests/ui/async-await/issue-68112.no_drop_tracking.stderr

80 lines
3.1 KiB
Plaintext
Raw Normal View History

Add test for #68112 (existing output)
2020-03-24 19:23:50 -05:00
error: future cannot be sent between threads safely
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:37:18
Add test for #68112 (existing output)
2020-03-24 19:23:50 -05:00
|
LL | require_send(send_fut);
Rework point-at-arg
2022-08-16 01:27:22 -05:00
| ^^^^^^^^ future created by async block is not `Send`
Add test for #68112 (existing output)
2020-03-24 19:23:50 -05: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 02:40:56 -05:00
= help: the trait `Sync` is not implemented for `RefCell<i32>`
Incorporate feedback into diagnostics
2020-04-08 13:54:31 -05:00
note: future is not `Send` as it awaits another future which is not `Send`
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:34:17
Add test for #68112 (existing output)
2020-03-24 19:23:50 -05:00
|
LL | let _ = non_send_fut.await;
Print output ty for opaque future ty
2021-11-16 18:16:23 -06: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 11:26:55 -05:00
note: required by a bound in `require_send`
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:14:25
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
|
LL | fn require_send(_: impl Send) {}
| ^^^^ required by this bound in `require_send`
Add test for #68112 (existing output)
2020-03-24 19:23:50 -05:00
Don't double-annotate the same Span
2020-04-01 21:04:55 -05:00
error: future cannot be sent between threads safely
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:46:18
Don't double-annotate the same Span
2020-04-01 21:04:55 -05:00
|
LL | require_send(send_fut);
Rework point-at-arg
2022-08-16 01:27:22 -05:00
| ^^^^^^^^ future created by async block is not `Send`
Don't double-annotate the same Span
2020-04-01 21:04:55 -05: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 02:40:56 -05:00
= help: the trait `Sync` is not implemented for `RefCell<i32>`
Incorporate feedback into diagnostics
2020-04-08 13:54:31 -05:00
note: future is not `Send` as it awaits another future which is not `Send`
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:43:17
Don't double-annotate the same Span
2020-04-01 21:04:55 -05:00
|
LL | let _ = make_non_send_future1().await;
Print output ty for opaque future ty
2021-11-16 18:16:23 -06: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 11:26:55 -05:00
note: required by a bound in `require_send`
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:14:25
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
|
LL | fn require_send(_: impl Send) {}
| ^^^^ required by this bound in `require_send`
Don't double-annotate the same Span
2020-04-01 21:04:55 -05: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 02:40:56 -05:00
error[E0277]: `RefCell<i32>` cannot be shared between threads safely
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:65:18
Add test for #68112 (existing output)
2020-03-24 19:23:50 -05:00
|
LL | require_send(send_fut);
Rework point-at-arg
2022-08-16 01:27:22 -05:00
| ------------ ^^^^^^^^ `RefCell<i32>` cannot be shared between threads safely
| |
| required by a bound introduced by this call
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
|
= help: the trait `Sync` is not implemented for `RefCell<i32>`
Reword "Required because of the requirements on the impl of ..."
2022-08-15 15:31:37 -05:00
= note: required for `Arc<RefCell<i32>>` to implement `Send`
Address review comments from #98259 It got merged so fast I didn't have time to make changes xD
2022-06-21 19:43:46 -05:00
note: required because it's used within this `async fn` body
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:50:31
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
|
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
LL | async fn ready2<T>(t: T) -> T {
| _______________________________^
LL | | t
LL | | }
| |_^
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 appears within the type `impl Future<Output = Arc<RefCell<i32>>>`
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:53:31
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
|
LL | fn make_non_send_future2() -> impl Future<Output = Arc<RefCell<i32>>> {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Revert "Replace usage of `ResumeTy` in async lowering with `Context`"
2022-12-19 13:24:59 -06:00
= note: required because it captures the following types: `ResumeTy`, `impl Future<Output = Arc<RefCell<i32>>>`, `()`, `i32`, `Ready<i32>`
Address review comments from #98259 It got merged so fast I didn't have time to make changes xD
2022-06-21 19:43:46 -05:00
note: required because it's used within this `async` block
Avoid `GenFuture` shim when compiling async constructs Previously, async constructs would be lowered to "normal" generators, with an additional `from_generator` / `GenFuture` shim in between to convert from `Generator` to `Future`. The compiler will now special-case these generators internally so that async constructs will *directly* implement `Future` without the need to go through the `from_generator` / `GenFuture` shim. The primary motivation for this change was hiding this implementation detail in stack traces and debuginfo, but it can in theory also help the optimizer as there is less abstractions to see through.
2022-11-18 15:56:22 -06:00
--> $DIR/issue-68112.rs:60:20
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
|
LL | let send_fut = async {
Avoid `GenFuture` shim when compiling async constructs Previously, async constructs would be lowered to "normal" generators, with an additional `from_generator` / `GenFuture` shim in between to convert from `Generator` to `Future`. The compiler will now special-case these generators internally so that async constructs will *directly* implement `Future` without the need to go through the `from_generator` / `GenFuture` shim. The primary motivation for this change was hiding this implementation detail in stack traces and debuginfo, but it can in theory also help the optimizer as there is less abstractions to see through.
2022-11-18 15:56:22 -06:00
| ____________________^
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
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 11:26:55 -05:00
note: required by a bound in `require_send`
Update issue-68114.rs
2022-09-13 16:36:45 -05:00
--> $DIR/issue-68112.rs:14:25
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
|
LL | fn require_send(_: impl Send) {}
| ^^^^ required by this bound in `require_send`
Add test for #68112 (existing output)
2020-03-24 19:23:50 -05:00
Don't double-annotate the same Span
2020-04-01 21:04:55 -05:00
error: aborting due to 3 previous errors
Add test for #68112 (existing output)
2020-03-24 19:23:50 -05:00
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink