about summary refs log tree commit diff
path: root/src/tools/rust-analyzer/docs
AgeCommit message (Collapse)AuthorLines
2025-01-10Implement implicit sized bound inlay hintsLukas Wirth-0/+5
2025-01-10Merge pull request #18813 from Giga-Bowser/syntax-tree-viewLukas Wirth-1/+18
feat: Add a new and improved syntax tree view
2025-01-09Remove the old syntax tree viewerGiga Bowser-1/+1
2025-01-09Add a new and improved syntax tree viewerGiga Bowser-1/+18
2025-01-09Merge pull request #18880 from PrototypeNM1/extra-includesLukas Wirth-0/+7
Add config setting which allows adding additional include paths to the VFS.
2025-01-08Add config setting which allows adding additional include paths to the VFS.Nicholas Rishel-0/+7
2025-01-08fix: autogenerate filesqjerome-4/+4
2025-01-07target-triple -> target-tupleLukas Wirth-2/+2
2025-01-07Remove `rust-analyzer.cargo.sysrootQueryMetadata` config againLukas Wirth-6/+0
2025-01-06fix: Be more permissive with completion resolve dataLukas Wirth-1/+1
2025-01-01Merge pull request #18179 from ChayimFriedman2/omit-trait-completionLukas Wirth-0/+38
feat: Allow excluding specific traits from completion
2025-01-01Revamp auto-import exclude configLukas Wirth-5/+16
2025-01-01Reduce the default autoimport exclusion listLukas Wirth-40/+3
2025-01-01Allow excluding specific traits from completionChayim Refael Friedman-0/+64
To be accurate, only their methods are excluded, the trait themselves are still available. I also excluded a bunch of std traits by default. Some less opinionated, like `AsRef`, which should never be used directly except in generic scenarios (and won't be excluded there), some more opinionated, like the ops traits, which I know some users sometimes want to use directly. Either way it's configurable. It should be pretty easy to extend support to excluding only specific methods, but I didn't do that currently. Traits configured to be excluded are resolved in each completion request from scratch. If this proves too expensive, it is easy enough to cache them in the DB.
2024-12-26fix incorrect name for UpdateTest configroife-1/+1
2024-12-26feat: add config `UpdateTest` to hover actionsroife-0/+6
2024-12-26feat: support UpdateTest in codelensroife-1/+7
2024-12-24Merge pull request #18707 from ChayimFriedman2/substLukas Wirth-0/+9
feat: Show substitution where hovering over generic things
2024-12-22fix: Properly check if workspace flychecking is allowedLukas Wirth-1/+2
2024-12-20Show substitution where hovering over generic thingsChayim Refael Friedman-0/+9
There are few things to note in the implementation: First, this is a best-effort implementation. Mainly, type aliases may not be shown (due to their eager nature it's harder) and partial pathes (aka. hovering over `Struct` in `Struct::method`) are not supported at all. Second, we only need to show substitutions in expression and pattern position, because in type position all generic arguments always have to be written explicitly.
2024-12-16internal: Don't serialize empty fields in completions and resolve payloadsLukas Wirth-1/+1
2024-12-11Fix publish workflow link in manualSam Estep-1/+1
2024-12-10Address the feedback from pascalkutheKirill Bulatov-1/+1
* Use Base64 to minify the hash representation in the JSON data * Do hash checks only for items with similar labels
2024-12-09Always compute the hash when r-a wants the imports to be resolvedKirill Bulatov-1/+1
2024-12-09Draft completion hashingKirill Bulatov-1/+1
2024-12-09Disable pipe on typing handlerLukas Wirth-1/+1
2024-12-06Add typing handler for param list pipeLukas Wirth-2/+2
2024-12-06Make bracket typing handler work on more thingsLukas Wirth-1/+1
2024-12-05Disable `<` typing handler againLukas Wirth-1/+1
2024-12-03chore: deprecate `typing.autoClosingAngleBrackets` configurationTarek-5/+0
Signed-off-by: Tarek <tareknaser360@gmail.com>
2024-12-03internal: Make exclude characters for typing assists configurable, default ↵Tarek-0/+5
to None Signed-off-by: Tarek <tareknaser360@gmail.com>
2024-11-26Merge pull request #18511 from darichey/sysroot-query-metadataLaurențiu Nicola-0/+6
Re-add `rust-analyzer.cargo.sysrootQueryMetadata`
2024-11-23Update request entry point file path in architecture.mdMark Murphy-1/+1
2024-11-18Re-add rust-analyzer.cargo.sysrootQueryMetadataDavid Richey-0/+6
2024-11-11Update the file hashKirill Bulatov-1/+1
2024-11-10Replace with C-ArchitectureSam Estep-0/+4
2024-11-07Delete design label from listSam Estep-4/+0
2024-10-30Merge pull request #18304 from davidkurilla/docs-create-setup-documentLukas Wirth-0/+57
docs: create setup documentation
2024-10-22docs: remove unnecessary prerequisites setup.mdDavid Kurilla-9/+3
2024-10-21Update ide testsLukas Wirth-22/+22
2024-10-18style: fix typosDavid Kurilla-3/+3
2024-10-18docs: create setup documentationDavid Kurilla-0/+63
2024-10-13feat: respect references.exclude_tests in call-hierarchyroife-1/+1
2024-10-04internal: add JSON formatting for hprofDavid Barsky-1/+9
2024-09-30Auto merge of #18167 - SomeoneToIgnore:fat-completions, r=Veykrilbors-1/+1
internal: Send less data during `textDocument/completion` if possible Similar to https://github.com/rust-lang/rust-analyzer/pull/15522, stops sending extra data during `textDocument/completion` if that data was set in the client completions resolve capabilities, and sends those only during `completionItem/resolve` requests. Currently, rust-analyzer sends back all fields (including potentially huge docs) for every completion item which might get large. Same as the other one, this PR aims to keep the changes minimal and does not remove extra computations for such fields — instead, it just filters them out before sending to the client. The PR omits primitive, boolean and integer, types such as `deprecated`, `preselect`, `insertTextFormat`, `insertTextMode`, etc. AND `additionalTextEdits` — this one looks very dangerous to compute for each completion item (as the spec says we ought to if there's no corresponding resolve capabilities provided) due to the diff computations and the fact that this code had been in the resolution for some time. It would be good to resolve this lazily too, please let me know if it's ok to do. When tested with Zed which only defines `documentation` and `additionalTextEdits` in its client completion resolve capabilities, rust-analyzer starts to send almost 3 times less characters: Request: ```json {"jsonrpc":"2.0","id":104,"method":"textDocument/completion","params":{"textDocument":{"uri":"file:///Users/someonetoignore/work/rust-analyzer/crates/ide/src/inlay_hints.rs"},"position":{"line":90,"character":14},"context":{"triggerKind":1}}} ``` <img width="1338" alt="image" src="https://github.com/user-attachments/assets/104f19b5-7095-4fc1-b008-5d829623b2e2"> Before: 381944 characters [before.json](https://github.com/user-attachments/files/17092385/before.json) After: 140503 characters [after.json](https://github.com/user-attachments/files/17092386/after.json) After Zed's [patch](https://github.com/zed-industries/zed/pull/18212) to enable all resolving possible: 84452 characters [after-after.json](https://github.com/user-attachments/files/17092755/after-after.json)
2024-09-30Auto merge of #18085 - ChayimFriedman2:gate-test, r=Veykrilbors-0/+5
feat: Provide an config option to not set `cfg(test)` Fixes #17957.
2024-09-30Provide an config option to not set `cfg(test)`Chayim Refael Friedman-0/+5
2024-09-29Rename object_safety to dyn_compatibilityNoah Bright-1/+1
Up to a trait implemented by another package, linking to $CARGO_HOME/registry/cache/index.crates.io-6f17d22bba15001f/
2024-09-28Update handlers.rs to handlers/requests.rsNoah Bright-1/+1
2024-09-23Fix the testKirill Bulatov-1/+1