diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-02-08 09:06:32 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-08 09:06:32 +0100 |
| commit | 9ec5960e3d1c1bdf6c74e9972668c39ffdac3026 (patch) | |
| tree | b9ffe32e4f915bf0d68442b4639f50528e1325f3 /compiler/rustc_pattern_analysis/src | |
| parent | 4e11d03d0e128c91ec48a1b69f2b6724557ffa60 (diff) | |
| parent | 1a3214b774f47b2fb8dadf305939f97e20993fe2 (diff) | |
| download | rust-9ec5960e3d1c1bdf6c74e9972668c39ffdac3026.tar.gz rust-9ec5960e3d1c1bdf6c74e9972668c39ffdac3026.zip | |
Rollup merge of #120103 - compiler-errors:concrete-afits, r=oli-obk
Make it so that async-fn-in-trait is compatible with a concrete future in implementation There's no technical reason why an AFIT like `async fn foo()` cannot be satisfied with an implementation signature like `fn foo() -> Pin<Box<dyn Future<Output = ()> + 'static>>`. We rejected this previously because we were uncertain about how AFITs worked with refinement, but I don't believe this needs to be a restriction any longer. r? oli-obk
Diffstat (limited to 'compiler/rustc_pattern_analysis/src')
0 files changed, 0 insertions, 0 deletions