diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2021-10-25 07:54:12 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-25 07:54:12 +0200 |
| commit | b25172b5048dce325e44b2e1c381acfe3815f957 (patch) | |
| tree | b8c727fdc667bbeb97319b7eb28286a5af10ea46 /src/test/rustdoc-ui/coverage/enum-tuple.rs | |
| parent | 28d0e75269ad092662fef27f44c6aa029c376d49 (diff) | |
| parent | 6dcff4e9f6badd8b7daf24c52d80dd6b89d12f4a (diff) | |
| download | rust-b25172b5048dce325e44b2e1c381acfe3815f957.tar.gz rust-b25172b5048dce325e44b2e1c381acfe3815f957.zip | |
Rollup merge of #89889 - estebank:unmet-send-bound-on-foreign-future, r=tmandry
Use the "nice E0277 errors"[1] for `!Send` `impl Future` from foreign crate Partly address #78543 by making the error quieter. We don't have access to the `typeck` tables from foreign crates, so we used to completely skip the new code when checking foreign crates. Now, we carry on and don't provide as nice output (we don't clarify *what* is making the `Future: !Send`), but at least we no longer emit a sea of derived obligations in the output. [1]: https://blog.rust-lang.org/inside-rust/2019/10/11/AsyncAwait-Not-Send-Error-Improvements.html r? `@tmandry`
Diffstat (limited to 'src/test/rustdoc-ui/coverage/enum-tuple.rs')
0 files changed, 0 insertions, 0 deletions