diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-02-25 10:02:21 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-02-25 10:02:21 +0000 |
| commit | 1fe48a0115c24240f5a3e1b329e642f18e2715d6 (patch) | |
| tree | 88c3290bced7671039b4765a5f599a019aa3c6e6 /editors/code/src/rust-analyzer-api.ts | |
| parent | 5e6f4ca6905e02a5fa34ef292fa2abefcd982222 (diff) | |
| parent | 17ffdf9c27a6bb5cf5d30ad6a677390609fcf861 (diff) | |
Merge #3159
3159: Server-side Semantic Tokens r=matklad a=kjeremy
Takes the output of `syntax_highlighting` and converts it to the proposed semantic tokens API (so far only `textDocument/semanticTokens`. There's a lot of cool stuff we could do with this and the "Inspect Editor Tokens and Scopes" vscode command (pic below) is a cool way to see what has tokens and what doesn't.
Incredibly hacky and could panic due to unwraps, `panic!` etc. To use: run with `code-insiders --enable-proposed-api matklad.rust-analyzer`. If you try to run this without `--enable-proposed-api` it will crash.
@matklad I'm mostly looking for design feedback.
Co-authored-by: kjeremy <[email protected]>
Co-authored-by: Jeremy Kolb <[email protected]>
Diffstat (limited to 'editors/code/src/rust-analyzer-api.ts')
0 files changed, 0 insertions, 0 deletions