diff options
| author | bors <bors@rust-lang.org> | 2023-12-26 04:25:53 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-12-26 04:25:53 +0000 |
| commit | 91859ed80a067d89f20a0883ffb3a3af277ce92c (patch) | |
| tree | 0a1f51ad525b0fdbbc7f2d6241fce0094430d82d /tests/codegen/src-hash-algorithm | |
| parent | 620a1e4c2fdea7f4282679fb68abc34823f99bea (diff) | |
| parent | e0097f5323f700768b2b8ceb217b4394ff447da6 (diff) | |
| download | rust-91859ed80a067d89f20a0883ffb3a3af277ce92c.tar.gz rust-91859ed80a067d89f20a0883ffb3a3af277ce92c.zip | |
Auto merge of #119258 - compiler-errors:closure-kind, r=eholk
Make closures carry their own ClosureKind Right now, we use the "`movability`" field of `hir::Closure` to distinguish a closure and a coroutine. This is paired together with the `CoroutineKind`, which is located not in the `hir::Closure`, but the `hir::Body`. This is strange and redundant. This PR introduces `ClosureKind` with two variants -- `Closure` and `Coroutine`, which is put into `hir::Closure`. The `CoroutineKind` is thus removed from `hir::Body`, and `Option<Movability>` no longer needs to be a stand-in for "is this a closure or a coroutine". r? eholk
Diffstat (limited to 'tests/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions