about summary refs log tree commit diff
path: root/tests/rustdoc-js-std/parser-tuple.js
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-03-05 22:10:00 +0100
committerGitHub <noreply@github.com>2024-03-05 22:10:00 +0100
commit2875b10a7e023f74ac70f66a13e12bd368226d08 (patch)
tree5d138ddefc7b951510725f0c7fcfb5cc50fdcb74 /tests/rustdoc-js-std/parser-tuple.js
parent0783a63d34c1b1a9959be7b8a4f585fbc5d783cb (diff)
parentd74d67c8369fd759d860d215aaa576a03d99b692 (diff)
downloadrust-2875b10a7e023f74ac70f66a13e12bd368226d08.tar.gz
rust-2875b10a7e023f74ac70f66a13e12bd368226d08.zip
Rollup merge of #121857 - compiler-errors:async-closure-signature-deduction, r=oli-obk
Implement async closure signature deduction

Self-explanatory from title.

Regarding the interaction between signature deduction, fulfillment, and the new trait solver: I'm not worried about implementing closure signature deduction here because:

1. async closures are unstable, and
2. I'm reasonably confident we'll need to support signature deduction in the new solver somehow (i.e. via proof trees, which seem very promising).

This is in contrast to #109338, which was closed because it generalizes signature deduction for a *stable* kind of expression (`async {}` blocks and `Future` traits), and which proliferated usage may pose a stabilization hazard for the new solver.

I'll be certain to make sure sure we revisit the closure signature deduction problem by the time that async closures are being stabilized (which isn't particularly soon) (edit: Put it into the async closure tracking issue). cc `````@lcnr`````

r? `````@oli-obk`````
Diffstat (limited to 'tests/rustdoc-js-std/parser-tuple.js')
0 files changed, 0 insertions, 0 deletions