diff options
| author | bors <bors@rust-lang.org> | 2024-10-09 15:35:33 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-10-09 15:35:33 +0000 |
| commit | 3e42fc55962fa19557ee2a34de192adebce11c47 (patch) | |
| tree | e76bbed8453bd2f771b23582d6763ea7f0051002 /tests/rustdoc-js-std/parser-errors.js | |
| parent | bd1c7e99d696b3bae0f960508f379bce0d802dd4 (diff) | |
| parent | 5544bf54e35e840b4fbfdebef4367978f76cc037 (diff) | |
| download | rust-3e42fc55962fa19557ee2a34de192adebce11c47.tar.gz rust-3e42fc55962fa19557ee2a34de192adebce11c47.zip | |
Auto merge of #18247 - jhgg:lsp/fix-something-to-resolve, r=Veykril
lsp: fix completion_item something_to_resolve not being a latch to true while looking at #18245 i noticed that `something_to_resolve` could technically flap between true -> false if some subsequent fields that were requested to be resolved were empty. this fixes that by using `|=` instead of `=` when assigning to `something_to_resolve` which will prevent it from going back to false once set. although some cases it's simply assigning to `true` i opted to continue to use `|=` there for uniformity sake. but happy to change those back to `=`'s. cc `@SomeoneToIgnore`
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions
