aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * Add status buffer function to emacs integrationFlorian Diebold2019-05-291-0/+34
| | | | | | | | Also fix a minor race condition in the 'extend selection' initialization.
* | Merge #1349bors[bot]2019-05-301-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | 1349: don't remove tools from cache r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | don't remove tools from cacheAleksey Kladov2019-05-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | On CI, we remove this project's artifacts from ./target before caching it. This way, cache never changes, because it only caches deps. We do this approximatelly, and, together with our own tools crate, we also remove itertools, which are used by some other deps. Given that tools change rarely, let's just cache them?
* | | Merge #1348bors[bot]2019-05-301-0/+5
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1348: cancel salsa's validation r=matklad a=matklad 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 Co-authored-by: Aleksey Kladov <[email protected]>
| * | 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
* | Merge #1346bors[bot]2019-05-295-2/+5
|\ \ | | | | | | | | | | | | | | | | | | | | | 1346: bump timeout for CI r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | bump timeout for CIAleksey Kladov2019-05-291-1/+1
| | |
| * | add cacellation checks to expensive queriesAleksey Kladov2019-05-293-0/+3
| | |
| * | less noisy statusAleksey Kladov2019-05-291-1/+1
| |/
* | Merge #1344bors[bot]2019-05-292-42/+55
|\ \ | |/ |/| | | | | | | | | | | 1344: Highlight primitive types r=matklad a=lnicola This is a hack to get better highlighting of primitive types until #1340. Co-authored-by: Laurențiu Nicola <[email protected]>
| * Highlight primitive typesLaurențiu Nicola2019-05-292-42/+55
|/
* Merge #1343bors[bot]2019-05-292-3/+16
|\ | | | | | | | | | | | | | | 1343: optimization: cancel backlog in onEnter r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * optimization: cancel backlog in onEnterAleksey Kladov2019-05-292-3/+16
| |
* | Merge #1342bors[bot]2019-05-293-12/+67
|\| | | | | | | | | | | | | | | 1342: add latest requests to status page r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * add latest requests to status pageAleksey Kladov2019-05-293-12/+67
| |
* | Merge #1341bors[bot]2019-05-291-19/+42
|\| | | | | | | | | | | | | | | 1341: log the actual time of requests r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * log the actual time of requestsAleksey Kladov2019-05-291-16/+31
| |
| * trigger garbage collection *after* requests, not beforeAleksey Kladov2019-05-291-2/+5
| |
| * more perf loggingAleksey Kladov2019-05-291-3/+8
|/
* Merge #1339bors[bot]2019-05-2947-297/+307
|\ | | | | | | | | | | | | | | 1339: flip Into to From r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * silnce profiling in testsAleksey Kladov2019-05-291-1/+2
| |
| * flip Into to FromAleksey Kladov2019-05-291-6/+6
| |
| * show error offsets in testsAleksey Kladov2019-05-2946-290/+299
|/
* Merge #1337bors[bot]2019-05-2989-687/+705
|\ | | | | | | | | | | | | | | 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-2829-91/+92
| |
| * fix syntax errors in testsAleksey Kladov2019-05-287-121/+137
| |
| * move mbe to the new APIAleksey Kladov2019-05-283-73/+73
| |
| * remove old parsing methodsAleksey Kladov2019-05-287-62/+54
| |
| * update test dataAleksey Kladov2019-05-2845-289/+290
| |
| * update testsAleksey Kladov2019-05-284-47/+36
| |
| * drop error from SOurceFile constructorAleksey Kladov2019-05-282-5/+5
| |
| * return errors from tree builderAleksey Kladov2019-05-282-5/+6
| |
| * drop errors from SyntaxNodeAleksey Kladov2019-05-282-9/+6
| |
| * add ParseAleksey Kladov2019-05-281-2/+26
| |
* | Merge #1338bors[bot]2019-05-292-3/+20
|\ \ | |/ |/| | | | | | | | | | | 1338: Highlight names correctly r=matklad a=lnicola Part of #1294. Co-authored-by: Laurențiu Nicola <[email protected]>
| * Highlight type names correctlyLaurențiu Nicola2019-05-292-3/+20
|/
* Merge #1336bors[bot]2019-05-284-156/+149
|\ | | | | | | | | | | | | | | 1336: Refactor SubtreeSource r=matklad a=edwin0cheng This PR simplify `SubtreeSource` by removing `SubtreeWalk` and `Querier` and only walk through the top level `TokenTree` when collecting token from source, by comparing two cursors directly. Co-authored-by: Edwin Cheng <[email protected]>
| * Use cfg(test) instead of allow(unused)Edwin Cheng2019-05-281-1/+1
| |
| * Minor use moduleEdwin Cheng2019-05-271-3/+2
| |
| * Simpliy how collecting token from srcEdwin Cheng2019-05-273-72/+39
| |
| * Add more helper func in CursorEdwin Cheng2019-05-271-0/+15
| |
| * Remove Queier and SubtreeWalkEdwin Cheng2019-05-272-92/+104
| |
* | Merge #1334bors[bot]2019-05-274-1/+87
|\ \ | |/ |/| | | | | | | | | | | 1334: check for cancellation during macro expansion r=matklad a=matklad closes #1331 Co-authored-by: Aleksey Kladov <[email protected]>
| * check cancellation when expanding macrosAleksey Kladov2019-05-272-3/+3
| |
| * specifically profile cancellationAleksey Kladov2019-05-271-0/+4
| |
| * enable profiling in testsAleksey Kladov2019-05-272-1/+83
| |
* | Merge #1319bors[bot]2019-05-2715-46/+242
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]>
| * | Make rainbows optionalPascal Hertleif2019-05-275-6/+29
| | |
| * | rename stray id fieldPascal Hertleif2019-05-272-2/+2
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 05:36:13 +0000