diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-06-24 06:27:14 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-06-24 06:27:14 +0200 |
| commit | bd0a886b7ee9a83b49c6ff7ef18c9a759073e915 (patch) | |
| tree | a9d9b78c7397b00a7091abf2db145feddd167b3d /tests/codegen/patchable-function-entry | |
| parent | 8f8a463cbd66122f1a47bc885a12c78d73532934 (diff) | |
| parent | 10277c97c23cc9ed55fe27d89f35cf8c2976e986 (diff) | |
| download | rust-bd0a886b7ee9a83b49c6ff7ef18c9a759073e915.tar.gz rust-bd0a886b7ee9a83b49c6ff7ef18c9a759073e915.zip | |
Rollup merge of #126754 - compiler-errors:use-rustfmt, r=calebcartwright
Implement `use<>` formatting in rustfmt This PR implements formatting for precise-capturing `use<>` syntax as proposed in https://github.com/rust-lang/rust/pull/126753. The syntax is implemented as-if the `use<>` bound were a trait bound but with the `use` keyword as its path segment identifier. I opted to develop this in the rust-lang/rust tree since I'm not certain when the next rustfmt subtree sync is going to be, and I'd rather not block landing nightly support for `use<>` on something I have no control over. If ``@rust-lang/rustfmt`` would rather I move this PR over to that repository, then I would at least like to know when the next rustfmt->rust subtree sync is going to be, since stabilizing `precise_capturing` without formatting will be disruptive. This implementation is otherwise rather straightforward. Tracking: - https://github.com/rust-lang/rust/issues/123432
Diffstat (limited to 'tests/codegen/patchable-function-entry')
0 files changed, 0 insertions, 0 deletions