diff options
| author | bors <bors@rust-lang.org> | 2023-09-06 20:32:04 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-09-06 20:32:04 +0000 |
| commit | 77b359ae31427051d62a8c7e39b56bc9798f23ed (patch) | |
| tree | b31600984ad36a8de15f151a62959d9e1f3162a9 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 5906c26e851cc554e986d5116d9536b16cebf8b4 (diff) | |
| parent | da786170f82717bba8086e6618382e57b5e98180 (diff) | |
| download | rust-77b359ae31427051d62a8c7e39b56bc9798f23ed.tar.gz rust-77b359ae31427051d62a8c7e39b56bc9798f23ed.zip | |
Auto merge of #15532 - SomeoneToIgnore:more-brackets-on-type-formatting, r=Veykril
On type format '(', by adding closing ')' automatically
If I understand right, `()` can surround pretty much the same `{}` can, so add another on type formatting pair for convenience: sometimes it's not that pleasant to write parenthesis in `Some(2).map(|i| (i, i+1))` cases and I would prefer r-a to do that for me.
One note: currently, https://github.com/rust-lang/rust-analyzer/blob/b06503b6ec98c9ed44698870cbf3302b8560b442/crates/rust-analyzer/src/handlers/request.rs#L357 fires always.
Should we remove the assertion entirely now, since apparently things work in release despite that check?
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions