aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_ide_api
Commit message (Collapse)AuthorAgeFilesLines
...
* one macro def should be enoughAleksey Kladov2019-06-082-6/+4
|
* Merge #1377bors[bot]2019-06-0614-644/+580
|\ | | | | | | | | | | | | | | 1377: Use inline snapshots in complete_keyword r=matklad a=sbihel Relates to #1127 Co-authored-by: Simon Bihel <[email protected]>
| * Use inline snapshots in complete_keywordSimon Bihel2019-06-0414-644/+580
| |
* | Fix clippy::or_fun_callAlan Du2019-06-042-2/+2
| |
* | Fix clippy::identity_conversionAlan Du2019-06-042-3/+2
| |
* | Fix clippy::new_without_defaultAlan Du2019-06-041-0/+6
| |
* | Fix clippy::assign_op_patternAlan Du2019-06-041-1/+1
| |
* | Fix clippy::useless_formatAlan Du2019-06-041-2/+2
| |
* | Fix clippy::into_iter_on_refAlan Du2019-06-041-1/+1
| |
* | Fix clippy::len_zeroAlan Du2019-06-041-2/+2
| |
* | Fix clippy::ptr_argAlan Du2019-06-041-2/+2
| |
* | Fix clippy::match_ref_patsAlan Du2019-06-041-6/+6
| |
* | Fix clippy::single_matchAlan Du2019-06-041-4/+3
|/
* don't cache parses twiceAleksey Kladov2019-06-022-7/+29
| | | | | | | | | Before this commit, `Parse`s for original file ended up two times in salsa's db: first, when we parse original file, and second, when we parse macro or a file. Given that parse trees are the worst ofenders in terms of memory, it makes sense to make sure we store them only once.
* collect macro queriesAleksey Kladov2019-06-021-0/+3
|
* add AstDatabaseAleksey Kladov2019-06-021-2/+3
|
* collect types and bodiesAleksey Kladov2019-06-011-0/+4
|
* collect impl source mapsAleksey Kladov2019-06-011-0/+1
|
* don't cache ast_id_to_nodeAleksey Kladov2019-06-011-1/+0
|
* show macro expanded trees in the stats as wellAleksey Kladov2019-06-011-7/+8
|
* Improve goto definition for MBEEdwin Cheng2019-06-012-1/+24
|
* Sort hover results in testsLaurențiu Nicola2019-05-301-2/+8
|
* update ra_ide_api to use builtinsAleksey Kladov2019-05-307-55/+81
|
* :arrow_up: parking_lotAleksey Kladov2019-05-301-1/+0
|
* cancel salsa's validationAleksey Kladov2019-05-301-0/+5
| | | | | | | | | | | | | | | | | | | This small fix should improve rust-analyzer resopnsivness for real-time operations like onEnter handling. Turns out, salsa's validation can take hundreds of milliseconds, and, in case no changes were made, it won't be triggering any queries. Because we check for cancellation in queries, that means that validation is not cancellable! What this PR does is injecting check_canceled checks into validation, by using salsa's event API, which wasn't meant to be used like this, but, hey, it works! Here's the onEnter handling before and after this change: https://youtu.be/7-ffPzgvH7o
* Highlight primitive typesLaurențiu Nicola2019-05-292-42/+55
|
* Merge #1337bors[bot]2019-05-2924-69/+68
|\ | | | | | | | | | | | | | | 1337: Move syntax errors our of syntax tree r=matklad a=matklad I am not really sure if it's a good idea, but `SyntaxError` do not really belong to a `SyntaxTree`. So let's just store them on the side? Co-authored-by: Aleksey Kladov <[email protected]>
| * fix todoAleksey Kladov2019-05-281-3/+0
| |
| * fix typos in mbe testsAleksey Kladov2019-05-2824-68/+70
| |
* | Highlight type names correctlyLaurențiu Nicola2019-05-292-3/+20
|/
* Merge #1334bors[bot]2019-05-271-0/+4
|\ | | | | | | | | | | | | | | 1334: check for cancellation during macro expansion r=matklad a=matklad closes #1331 Co-authored-by: Aleksey Kladov <[email protected]>
| * specifically profile cancellationAleksey Kladov2019-05-271-0/+4
| |
* | make it build againPascal Hertleif2019-05-271-12/+26
| |
* | Disable broken struct field rainbowingPascal Hertleif2019-05-273-23/+7
| |
* | More clever highlighting, incl draft for structsPascal Hertleif2019-05-277-407/+152
| |
* | Hash based on binding name and shadow counterPascal Hertleif2019-05-273-20/+75
| |
* | Semantic highlighting spikePascal Hertleif2019-05-273-35/+345
|/ | | | | | | | | | 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?
* Colorize Rust code as HTMLAleksey Kladov2019-05-254-152/+131
|
* :arrow_up: rustcAleksey Kladov2019-05-2358-610/+640
|
* profile highlightingAleksey Kladov2019-05-231-0/+3
|
* add union to code_modelAleksey Kladov2019-05-234-0/+11
|
* Improve highlighting of name refsLaurențiu Nicola2019-05-232-9/+168
|
* Move NameRef classification logic out of reference_definitionLaurențiu Nicola2019-05-234-97/+143
|
* Merge #1299bors[bot]2019-05-211-1/+18
|\ | | | | | | | | | | | | | | | | | | | | | | | | 1299: Use ThemeColor and add support for light themes r=matklad a=lnicola Part of #1294. - switch to `ThemeColor` - add light and high contrast theme definitions - highlight control flow keywords and `unsafe` Co-authored-by: Laurențiu Nicola <[email protected]>
| * Address feedbackLaurențiu Nicola2019-05-211-4/+11
| |
| * Use ThemeColor and add support for light themesLaurențiu Nicola2019-05-211-1/+11
| |
* | :arrow_up: instaAleksey Kladov2019-05-211-1/+1
|/
* apply T! macro where it is possibleSergey Parilin2019-05-155-13/+13
|
* expand to syntax nodeAleksey Kladov2019-05-141-1/+1
|
* make AstId untypedAleksey Kladov2019-05-133-5/+5
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-13 00:56:29 +0000