aboutsummaryrefslogtreecommitdiff
path: root/docs/user/features.md
diff options
context:
space:
mode:
authorbors[bot] <bors[bot]@users.noreply.github.com>2019-05-27 10:56:06 +0100
committerbors[bot] <bors[bot]@users.noreply.github.com>2019-05-27 10:56:06 +0100
commit0d1c6076073c73f57340e256dc25da9d37311ef0 (patch)
tree60ff1f4a42f8ef297c07d5716af67e3057c8e1bd /docs/user/features.md
parent4b48cff022a1606bde596f01fbf44361640b10d8 (diff)
parent1e6ba1901550fb1610a1a464c48ec358cd3c339c (diff)
Merge #1319
1319: Rainbow highlighting spike 🌈 r=killercup a=killercup Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request? Co-authored-by: Pascal Hertleif <[email protected]>
Diffstat (limited to 'docs/user/features.md')
-rw-r--r--docs/user/features.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/docs/user/features.md b/docs/user/features.md
index 22470bc56..b6e6008c4 100644
--- a/docs/user/features.md
+++ b/docs/user/features.md
@@ -470,3 +470,12 @@ There also snippet completions:
470 470
471- `tfn` -> `#[test] fn f(){}` 471- `tfn` -> `#[test] fn f(){}`
472 472
473### Code highlighting
474
475Experimental feature to let rust-analyzer highlight Rust code instead of using the
476default highlighter.
477
478#### Rainbow highlighting
479
480Experimental feature that, given code highlighting using rust-analyzer is
481active, will pick unique colors for identifiers.