mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

One more tiny doc fix

Browse Source
This commit is contained in:
Kirill Bulatov 2020-02-22 13:52:49 +03:00 committed by GitHub
parent 68c34d1f63
commit 6f8d70363d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/user/features.md
View File

@ -177,7 +177,7 @@ Two types of inlay hints are displayed currently:
In VS Code, the following settings can be used to configure the inlay hints: In VS Code, the following settings can be used to configure the inlay hints:
* `rust-analyzer.displayInlayHints` — toggles inlay hints display on or off * `rust-analyzer.displayInlayHints` — toggles inlay hints display on or off
* rust-analyzer.maxInlayHintLength — shortens the hints if their length exceeds the value specified. If no value is specified (`null`), no shorteninng is applied. * `rust-analyzer.maxInlayHintLength` — shortens the hints if their length exceeds the value specified. If no value is specified (`null`), no shorteninng is applied.
**Note:** VS Code does not have native support for inlay hints [yet](https://github.com/microsoft/vscode/issues/16221) and the hints are implemented using decorations. **Note:** VS Code does not have native support for inlay hints [yet](https://github.com/microsoft/vscode/issues/16221) and the hints are implemented using decorations.
This approach has limitations: the caret movement near the end of the hint may look [weird](https://github.com/rust-analyzer/rust-analyzer/issues/1623). This approach has limitations: the caret movement near the end of the hint may look [weird](https://github.com/rust-analyzer/rust-analyzer/issues/1623).