diff options
| author | bors <bors@rust-lang.org> | 2023-06-10 11:15:16 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-06-10 11:15:16 +0000 |
| commit | 489eeab978a5e91bb7102d1625f468d95a7a4dcf (patch) | |
| tree | eb6526b8ccd0c7ea2aa075497951857bac661c24 /tests/mir-opt/lower_array_len.array_bound.NormalizeArrayLen.panic-unwind.diff | |
| parent | 49b4f15973a8b5d7c737d9c682b00b797d4143fd (diff) | |
| parent | ad2a0d109330952b6bc15fba43dffccce7f96a70 (diff) | |
| download | rust-489eeab978a5e91bb7102d1625f468d95a7a4dcf.tar.gz rust-489eeab978a5e91bb7102d1625f468d95a7a4dcf.zip | |
Auto merge of #14960 - jneem:group-delim-span, r=Veykril
Add span to group. This appears to fix #14959, but I've never contributed to rust-analyzer before and there were some things that confused me: - I had to add the `fn byte_range` method to get it to build. This was added to rust in [April](https://github.com/rust-lang/rust/pull/109002), so I don't understand why it wasn't needed until now - When testing, I ran into the fact that rust recently updated its `METADATA_VERSION`, so I had to test this with nightly-2023-05-20. But then I noticed that rust has its own copy of `rust-analyzer`, and the metadata version bump has already been [handled there](https://github.com/rust-lang/rust/commit/60e95e76d059e3bbeb19d819914df3bcf7684a82). So I guess I don't really understand the relationship between the code there and the code here.
Diffstat (limited to 'tests/mir-opt/lower_array_len.array_bound.NormalizeArrayLen.panic-unwind.diff')
0 files changed, 0 insertions, 0 deletions