rust/crates
Pascal Hertleif 5bf3e949e8
Semantic highlighting spike
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?
2019-05-27 11:26:33 +02:00
..
gen_lsp_server updated gen_lsp_server examples 2019-05-22 20:35:12 -05:00
ra_arena Add is_empty to Arena 2019-04-26 11:42:10 -04:00
ra_assists Merge #1281 2019-05-22 07:39:54 +00:00
ra_batch migrate to salsas interning 2019-04-09 22:51:22 +03:00
ra_cli Colorize Rust code as HTML 2019-05-25 13:42:34 +03:00
ra_db add profile calls to parsing/expansion routines 2019-05-22 11:31:07 +03:00
ra_fmt apply T! macro where it is possible 2019-05-15 15:35:47 +03:00
ra_hir Formatting 2019-05-27 15:37:22 +08:00
ra_ide_api Semantic highlighting spike 2019-05-27 11:26:33 +02:00
ra_lsp_server Semantic highlighting spike 2019-05-27 11:26:33 +02:00
ra_mbe Remove duplicated code 2019-05-26 02:41:00 +08:00
ra_parser Merge #1328 2019-05-27 07:28:13 +00:00
ra_prof better profilig 2019-05-22 00:00:58 +03:00
ra_project_model Sends cwd info for runnables and code lenses 2019-04-14 10:04:38 +02:00
ra_syntax Semantic highlighting spike 2019-05-27 11:26:33 +02:00
ra_text_edit Disable fork feature for proptest 2019-03-23 08:57:07 +01:00
ra_tt Use slice instead of Vec 2019-05-23 21:05:22 +08:00
test_utils fix error on wrong path 2019-03-17 12:53:22 +03:00
thread_worker
tools Use EXE extension for pre-commit hook on Window 2019-03-27 07:52:59 +01:00