diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2024-02-29 14:33:50 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-29 14:33:50 +0100 |
| commit | 5978b6ff8388574559b3c52c6c975f94a34c6ed9 (patch) | |
| tree | 1d07f193c943a627975425d6a34812966d09f4c7 /tests/rustdoc-js-std/parser-slice-array.js | |
| parent | 1ee54538a3bc5628b2a26b70fa0420091b2bb7a5 (diff) | |
| parent | c8e3f35eb631c35bc7aabf358b7ca5c2a7fbfd1e (diff) | |
| download | rust-5978b6ff8388574559b3c52c6c975f94a34c6ed9.tar.gz rust-5978b6ff8388574559b3c52c6c975f94a34c6ed9.zip | |
Rollup merge of #121654 - compiler-errors:async-fn-for-fn-def, r=oli-obk
Fix `async Fn` confirmation for `FnDef`/`FnPtr`/`Closure` types
Fixes three issues:
1. The code in `extract_tupled_inputs_and_output_from_async_callable` was accidentally getting the *future* type and the *output* type (returned by the future) messed up for fnptr/fndef/closure types. :/
2. We have a (class of) bug(s) in the old solver where we don't really support higher ranked built-in `Future` goals for generators. This is not possible to hit on stable code, but [can be hit with `unboxed_closures`](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=e935de7181e37e13515ad01720bcb899) (#121653).
* I'm opting not to fix that in this PR. Instead, I just instantiate placeholders when confirming `async Fn` goals.
4. Fixed a bug when generating `FnPtr` shims for `async Fn` trait goals.
r? oli-obk
Diffstat (limited to 'tests/rustdoc-js-std/parser-slice-array.js')
0 files changed, 0 insertions, 0 deletions