diff options
| author | bors <bors@rust-lang.org> | 2023-05-15 09:16:51 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-05-15 09:16:51 +0000 |
| commit | bc0341812795410fab08c535c41a0ecf7d7cb510 (patch) | |
| tree | 2469e5276a2704f964802d80c70768ccff7fca9c /tests/mir-opt/lower_array_len.array_len.NormalizeArrayLen.panic-unwind.diff | |
| parent | e5c722820ac6f348c6c674ef3391d7156f1cd1c9 (diff) | |
| parent | fa2340a4dfb70834259ad704f0b3a13021fa1b54 (diff) | |
| download | rust-bc0341812795410fab08c535c41a0ecf7d7cb510.tar.gz rust-bc0341812795410fab08c535c41a0ecf7d7cb510.zip | |
Auto merge of #14746 - lowr:patch/associated-return-types, r=Veykril
Parse associated return type bounds This PR implements parser support for associated return type bounds: `T: Foo<bar(): Send>`. This PR does not implement associated return types (`T::bar(): Send`) because it's not implemented even in rustc, and also removes `(..)`-style return type notation because it has been removed in rust-lang/rust#110203 (effectively reverting #14465). I don't plan to proactively follow this unstable feature unless an RFC is accepted and my main motivation here is to remove no-longer-valid syntax `(..)` from our parser, nevertheless adding minimal parser support so anyone interested (as can be seen in #14465) can experiment it without rust-analyzer's syntax errors.
Diffstat (limited to 'tests/mir-opt/lower_array_len.array_len.NormalizeArrayLen.panic-unwind.diff')
0 files changed, 0 insertions, 0 deletions