diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-02-12 23:18:53 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-12 23:18:53 +0100 |
| commit | 41227f964a5c75abeeb0a5d43c920275dffd9921 (patch) | |
| tree | c6eabc1363cefd76338c9c5cf1b89cdbd47ad301 /tests/codegen/patchable-function-entry/patchable-function-entry-both-flags.rs | |
| parent | dbccecf375caa3c4e162b34315f12c44ec103bb7 (diff) | |
| parent | 4fbd5cc31fad26f5cb439ece09e634310c6868ae (diff) | |
| download | rust-41227f964a5c75abeeb0a5d43c920275dffd9921.tar.gz rust-41227f964a5c75abeeb0a5d43c920275dffd9921.zip | |
Rollup merge of #120950 - compiler-errors:miri-async-closurs, r=RalfJung,oli-obk
Fix async closures in CTFE First commit renames `is_coroutine_or_closure` into `is_closure_like`, because `is_coroutine_or_closure_or_coroutine_closure` seems confusing and long. Second commit fixes some forgotten cases where we want to handle `TyKind::CoroutineClosure` the same as closures and coroutines. The test exercises the change to `ValidityVisitor::aggregate_field_path_elem` which is the source of #120946, but not the change to `UsedParamsNeedSubstVisitor`, though I feel like it's not that big of a deal. Let me know if you'd like for me to look into constructing a test for the latter, though I have no idea what it'd look like (we can't assert against `TooGeneric` anywhere?). Fixes #120946 r? oli-obk cc ``@RalfJung``
Diffstat (limited to 'tests/codegen/patchable-function-entry/patchable-function-entry-both-flags.rs')
0 files changed, 0 insertions, 0 deletions