diff options
author | bors[bot] <bors[bot]@users.noreply.github.com> | 2019-05-27 10:56:06 +0100 |
---|---|---|
committer | bors[bot] <bors[bot]@users.noreply.github.com> | 2019-05-27 10:56:06 +0100 |
commit | 0d1c6076073c73f57340e256dc25da9d37311ef0 (patch) | |
tree | 60ff1f4a42f8ef297c07d5716af67e3057c8e1bd /docs | |
parent | 4b48cff022a1606bde596f01fbf44361640b10d8 (diff) | |
parent | 1e6ba1901550fb1610a1a464c48ec358cd3c339c (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')
-rw-r--r-- | docs/user/features.md | 9 |
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 | |||
475 | Experimental feature to let rust-analyzer highlight Rust code instead of using the | ||
476 | default highlighter. | ||
477 | |||
478 | #### Rainbow highlighting | ||
479 | |||
480 | Experimental feature that, given code highlighting using rust-analyzer is | ||
481 | active, will pick unique colors for identifiers. | ||