rust/src/test/ui/async-await/issues/issue-67893.rs

// aux-build: issue_67893.rs
// edition:2018

extern crate issue_67893;

fn g(_: impl Send) {}

fn main() {
    g(issue_67893::run())
    //~^ ERROR generator cannot be sent between threads safely
}
Add test for issue-67893 2020-04-16 10:09:59 +09:00			`// aux-build: issue_67893.rs`
			`// edition:2018`

			`extern crate issue_67893;`

			`fn g(_: impl Send) {}`

			`fn main() {`
			`g(issue_67893::run())`
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 2021-10-14 17:57:39 +00:00			`//~^ ERROR generator cannot be sent between threads safely`
Add test for issue-67893 2020-04-16 10:09:59 +09:00			`}`