diff options
| author | Michael Goulet <michael@errs.io> | 2023-03-30 12:42:20 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-30 12:42:20 -0700 |
| commit | 7cd96ae2d7b596a95f53e3edabed589b899e5407 (patch) | |
| tree | 3ffe8d58607b409032fffb1e179ab8f639f48485 /compiler/rustc_const_eval/src | |
| parent | fbe738345cfe845f0d3b7b0961258187c3d26550 (diff) | |
| parent | 177997e3833d48973e7856e14f2935340b1862f1 (diff) | |
| download | rust-7cd96ae2d7b596a95f53e3edabed589b899e5407.tar.gz rust-7cd96ae2d7b596a95f53e3edabed589b899e5407.zip | |
Rollup merge of #109739 - compiler-errors:new-solver-closure-fnonce, r=lcnr
Closures always implement `FnOnce` in new solver We should process `[closure]: FnOnce(Tys...) -> Ty` obligations *before* fallback and closure analysis. We can do this by taking advantage of the fact that `FnOnce` is always implemented by closures, even before we definitely know the closure kind. Fixes compiler-errors/next-solver-hir-issues#15 r? ``@oli-obk`` (trying to spread the reviewer load for new trait solver prs, and this one is pretty self-contained, though feel free to reassign 😸)
Diffstat (limited to 'compiler/rustc_const_eval/src')
0 files changed, 0 insertions, 0 deletions