aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* Merge #75bors[bot]2018-09-191-1/+1
|\ | | | | | | | | | | | | | | 75: libsyntax2 -> rust-analyzer r=matklad a=kjeremy Change a few `libsyntax2` to `rust-analyzer` Co-authored-by: Jeremy A. Kolb <[email protected]>
| * libsyntax2 -> rust-analyzerJeremy A. Kolb2018-09-181-1/+1
| |
* | prefer lifetimes in extend selectionAleksey Kladov2018-09-191-1/+13
| |
* | Add emacs function for extend shirnk selectionAleksey Kladov2018-09-183-3/+37
|/
* eprintlnAleksey Kladov2018-09-161-7/+37
|
* rename all thingsAleksey Kladov2018-09-16468-107/+107
|
* fix derecated callAleksey Kladov2018-09-161-2/+2
|
* fix installation for windowsAleksey Kladov2018-09-161-3/+11
|
* get rid of commandspeckAleksey Kladov2018-09-162-22/+21
|
* Merge #67bors[bot]2018-09-1518-453/+1285
|\ | | | | | | | | | | | | | | | | | | | | | | 67: Salsa r=matklad a=matklad The aim of this PR is to transition from rather ad-hock FileData and ModuleMap caching strategy to something resembling a general-purpose red-green engine. Ideally, we shouldn't recompute ModuleMap at all, unless the set of mod decls or files changes. Co-authored-by: Aleksey Kladov <[email protected]>
| * everysalsaAleksey Kladov2018-09-154-23/+40
| |
| * kill old module_mapAleksey Kladov2018-09-159-540/+239
| |
| * move readonly source to module tree descrAleksey Kladov2018-09-152-17/+25
| |
| * ModuleTreeDescriptorAleksey Kladov2018-09-158-138/+306
| |
| * yet another db apiAleksey Kladov2018-09-155-258/+274
| |
| * minorAleksey Kladov2018-09-152-2/+3
| |
| * renamesAleksey Kladov2018-09-153-47/+49
| |
| * use salsa for new module mapAleksey Kladov2018-09-158-395/+318
| |
| * eager invalidationAleksey Kladov2018-09-152-12/+76
| |
| * be generic over dataAleksey Kladov2018-09-152-55/+61
| |
| * generic salsa algoAleksey Kladov2018-09-153-0/+399
| |
| * store params in the graphAleksey Kladov2018-09-151-5/+7
| |
| * any-cacheAleksey Kladov2018-09-152-21/+18
| |
| * fix dep trackingAleksey Kladov2018-09-152-31/+18
| |
| * add deps trackingAleksey Kladov2018-09-153-47/+148
| |
| * Add simplisitc global modification cachingAleksey Kladov2018-09-153-31/+111
| |
| * initial query tracingAleksey Kladov2018-09-152-13/+55
| |
| * start query-based modulesAleksey Kladov2018-09-157-41/+361
| |
* | Merge #69bors[bot]2018-09-154-198/+360
|\ \ | |/ |/| | | | | | | | | | | 69: Incremental reparsing for single tokens r=matklad a=darksv Implement incremental reparsing for `WHITESPACE`, `COMMENT`, `DOC_COMMENT`, `IDENT`, `STRING` and `RAW_STRING`. This allows to avoid reparsing whole blocks when a change was made only within these tokens. Co-authored-by: darksv <[email protected]>
| * independent tests for incremental reparsing of blocks and leavesdarksv2018-09-151-48/+68
| |
| * move reparsing testsdarksv2018-09-153-129/+140
| |
| * commit missing filedarksv2018-09-151-1/+1
| |
| * create separated mod for reparsing functionalitydarksv2018-09-153-170/+200
| |
| * correctly handle IDENTs when changed to contextual keywordsdarksv2018-09-141-1/+15
| |
| * create leaf directly without calling the parserdarksv2018-09-141-23/+2
| |
| * Incremental reparsing for single tokens (WHITESPACE, COMMENT, DOC_COMMENT, ↵darksv2018-09-132-14/+122
| | | | | | | | IDENT, STRING, RAW_STRING)
* | adjust trailing newlinedarksv2018-09-142-2/+4
| |
* | add missing files with inline testsdarksv2018-09-142-0/+13
| |
* | Support for unionsdarksv2018-09-144-7/+161
|/
* don't get stuck in slice patternsAleksey Kladov2018-09-122-21/+122
|
* correctly setup path-map for fs-changesAleksey Kladov2018-09-121-23/+24
|
* Merge #68bors[bot]2018-09-119-28/+98
|\ | | | | | | | | | | | | | | 68: Implement incremental reparsing for remaining braced blocks r=matklad a=darksv Fixes #66 Co-authored-by: darksv <[email protected]>
| * Do not reparse token tree when it is not delimited by bracesdarksv2018-09-102-1/+6
| |
| * Implement reparsing for remaining blocksdarksv2018-09-109-28/+93
| |
* | store file rsovlerAleksey Kladov2018-09-107-116/+146
|/
* Merge #65bors[bot]2018-09-081-1/+1
|\ | | | | | | | | | | | | | | 65: simplify r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * simplifyAleksey Kladov2018-09-081-1/+1
| |
* | Fix yet another parser infinite loopAleksey Kladov2018-09-082-8/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit is an example of fixing a common parser error: infinite loop due to error recovery. This error typically happens when we parse a list of items and fail to parse a specific item at the current position. One choices is to skip a token and try to parse a list item at the next position. This is a good, but not universal, default. When parsing a list of arguments in a function call, you, for example, don't want to skip over `fn`, because it's most likely that it is a function declaration, and not a mistyped arg: ``` fn foo() { quux(1, 2 fn bar() { } ``` Another choice is to bail out of the loop immediately, but it isn't perfect either: sometimes skipping over garbage helps: ``` quux(1, foo:, 92) // should skip over `:`, b/c that's part of `foo::bar` ``` In general, parser tries to balance these two cases, though we don't have a definitive strategy yet. However, if the parser accidentally neither skips over a token, nor breaks out of the loop, then it becomes stuck in the loop infinitely (there's an internal counter to self-check this situation and panic though), and that's exactly what is demonstrated by the test. To fix such situation, first of all, add the test case to tests/data/parser/{err,fuzz-failures}. Then, run ``` RUST_BACKTRACE=short cargo test --package libsyntax2 ```` to verify that parser indeed panics, and to get an idea what grammar production is the culprit (look for `_list` functions!). In this case, I see ``` 10: libsyntax2::grammar::expressions::atom::match_arm_list at crates/libsyntax2/src/grammar/expressions/atom.rs:309 ``` and that's look like it might be a culprit. I verify it by adding `eprintln!("loopy {:?}", p.current());` and indeed I see that this is printed repeatedly. Diagnosing this a bit shows that the problem is that `pattern::pattern` function does not consume anything if the next token is `let`. That is a good default to make cases like ``` let let foo = 92; ``` where the user hasn't typed the pattern yet, to parse in a reasonable they correctly. For match arms, pretty much the single thing we expect is a pattern, so, for a fix, I introduce a special variant of pattern that does not do recovery.
* | Add fuzz failures dirAleksey Kladov2018-09-082-4/+213
|/
* move fuzz-invariants to the libraryAleksey Kladov2018-09-083-41/+44
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-11 23:46:13 +0000