aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* Merge #5101bors[bot]2020-06-307-12/+361
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5101: Add expect -- a light-weight alternative to insta r=matklad a=matklad This PR implements a small snapshot-testing library. Snapshot updating is done by setting an env var, or by using editor feature (which runs a test with env-var set). Here's workflow for updating a failing test: ![expect](https://user-images.githubusercontent.com/1711539/85926956-28afa080-b8a3-11ea-9260-c6d0d8914d0b.gif) Here's workflow for adding a new test: ![expect-fresh](https://user-images.githubusercontent.com/1711539/85926961-306f4500-b8a3-11ea-9369-f2373e327a3f.gif) Note that colorized diffs are not implemented in this PR, but should be easy to add (we already use them in test_utils). Main differences from insta (which is essential for rust-analyzer development, thanks @mitsuhiko!): * self-updating tests, no need for a separate tool * fewer features (only inline snapshots, no redactions) * fewer deps (no yaml, no persistence) * tighter integration with editor * first-class snapshot object, which can be used to write test functions (as opposed to testing macros) * trivial to tweak for rust-analyzer needs, by virtue of being a workspace member. I think eventually we should converge to a single snapshot testing library, but I am not sure that `expect` is exactly right, so I suggest rolling with both insta and expect for some time (if folks agree that expect might be better in the first place!). # Editor Integration Implementation The thing I am most excited about is the ability to update a specific snapshot from the editor. I want this to be available to other snapshot-testing libraries (cc @mitsuhiko, @aaronabramov), so I want to document how this works. The ideal UI here would be a code action (:bulb:). Unfortunately, it seems like it is impossible to implement without some kind of persistence (if you save test failures into some kind of a database, like insta does, than you can read the database from the editor plugin). Note that it is possible to highlight error by outputing error message in rustc's format. Unfortunately, one can't use the same trick to implement a quick fix. For this reason, expect makes use of another rust-analyzer feature -- ability to run a single test at the cursor position. This does need some expect-specific code in rust-analyzer unfortunately. Specifically, if rust-analyzer notices that the cursor is on `expect!` macro, it adds a special flag to runnable's JSON. However, given #5017 it is possible to approximate this well-enough without rust-analyzer integration. Specifically, an extension can register a special runner which checks (using regexes) if rust-anlyzer runnable covers text with specific macro invocation and do special magic in that case. closes #3835 Co-authored-by: Aleksey Kladov <[email protected]>
| * Update crates/rust-analyzer/src/handlers.rsAleksey Kladov2020-06-281-3/+1
| | | | | | Co-authored-by: Veetaha <[email protected]>
| * Fix potential overflowAleksey Kladov2020-06-271-1/+1
| |
| * styleAleksey Kladov2020-06-271-2/+4
| |
| * Add colorsAleksey Kladov2020-06-272-5/+14
| |
| * Remove fragile testAleksey Kladov2020-06-271-29/+2
| | | | | | | | | | | | | | This test needs to be updated after every change (it contains line number), which is annoying. It also fails on windows due to \, so it's easier to remove it.
| * Update crates/expect/src/lib.rsAleksey Kladov2020-06-271-1/+1
| | | | | | Co-authored-by: bjorn3 <[email protected]>
| * Update crates/expect/src/lib.rsAleksey Kladov2020-06-271-2/+4
| | | | | | | | Co-authored-by: bjorn3 <[email protected]>
| * Add example expect test for goto definitionAleksey Kladov2020-06-272-8/+34
| |
| * Add light-weight snapshot testing library with editor integrationAleksey Kladov2020-06-275-4/+343
| |
* | Merge #5120bors[bot]2020-06-305-0/+71
|\ \ | | | | | | | | | | | | | | | | | | | | | 5120: Add a simple SSR subcommand to the rust-analyzer command line binary r=davidlattimore a=davidlattimore Is adding the dependency on ra_ide_db OK? It's needed for the call to `db.local_roots()` Co-authored-by: David Lattimore <[email protected]>
| * | Moved new deps to CLI-only sectionDavid Lattimore2020-06-301-2/+2
| | |
| * | Add a simple SSR subcommand to the rust-analyzer command line binaryDavid Lattimore2020-06-295-0/+71
| | |
| | |
| \ \
*-. \ \ Merge #5096 #5097bors[bot]2020-06-294-18/+37
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5096: Fix handling of whitespace when applying SSR within macro expansions. r=matklad a=davidlattimore I originally did replacement by passing in the full file text. Then as some point I thought I could do without it. Turns out calling .text() on a node coming from a macro expansion isn't a great idea, especially when you then try and use ranges from the original source to cut that text. The test I added here actually panics without the rest of this change (sorry I didn't notice sooner). 5097: Fix SSR prompt following #4919 r=matklad a=davidlattimore Co-authored-by: David Lattimore <[email protected]>
| * | | | Fix handling of whitespace when applying SSR within macro expansions.David Lattimore2020-06-274-18/+37
| | | | | | | | | | | | | | | | | | | | I originally did replacement by passing in the full file text. Then as some point I thought I could do without it. Turns out calling .text() on a node coming from a macro expansion isn't a great idea, especially when you then try and use ranges from the original source to cut that text. The test I added here actually panics without the rest of this change (sorry I didn't notice sooner).
* | | | | Merge #5122bors[bot]2020-06-291-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5122: Fix "Run | Debug" lens for examples r=matklad a=vsrs Fixes #4974 Co-authored-by: vsrs <[email protected]>
| * | | | | Fix "Run | Debug" lens for examplesvsrs2020-06-291-1/+1
| | |_|/ / | |/| | |
* | | | | Merge #5126bors[bot]2020-06-295-15/+20
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5126: Use more of FxHash* r=matklad a=lnicola ``` -rwxr-xr-x 1 me me 37917528 Jun 29 17:26 /home/me/.cargo/bin/rust-analyzer -rwxr-xr-x 1 me me 37904056 Jun 29 18:14 /home/me/.cargo/bin/rust-analyzer ``` Saved 13.5 KB there :-). Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | | | Use more of FxHash*Laurențiu Nicola2020-06-295-15/+20
| | | | | |
* | | | | | Update the rest of the testsAleksey Kladov2020-06-299-446/+311
| | | | | |
* | | | | | (T): make typification tests more data drivenAleksey Kladov2020-06-295-133/+137
|/ / / / /
* | | | | Merge #5124bors[bot]2020-06-295-21/+98
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5124: (Partially) fix handling of type params depending on type params r=matklad a=flodiebold If the first type parameter gets inferred, that's still not handled correctly; it'll require some more refactoring: E.g. if we have `Thing<T, F=fn() -> T>` and then instantiate `Thing<_>`, that gets turned into `Thing<_, fn() -> _>` before the `_` is instantiated into a type variable -- so afterwards, we have two type variables without any connection to each other. Co-authored-by: Florian Diebold <[email protected]>
| * | | | (Partially) fix handling of type params depending on type paramsFlorian Diebold2020-06-295-21/+98
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the first type parameter gets inferred, that's still not handled correctly; it'll require some more refactoring: E.g. if we have `Thing<T, F=fn() -> T>` and then instantiate `Thing<_>`, that gets turned into `Thing<_, fn() -> _>` before the `_` is instantiated into a type variable -- so afterwards, we have two type variables without any connection to each other.
* | | | | Merge #5105bors[bot]2020-06-2820-119/+44
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5105: Simlify with matches!() r=matklad a=Veetaha Co-authored-by: Veetaha <[email protected]>
| * | | | | Get rid of unused importsVeetaha2020-06-282-10/+3
| | | | | |
| * | | | | Follow matklad suggestionsVeetaha2020-06-285-19/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Move vis_offset() to utils.rs - Shorten explicit ra_syntax::ast -> ast - Undo refactoring exhaustive pattern to non-exhaustive
| * | | | | Simlify with matches!()Veetaha2020-06-2820-98/+32
| | | | | |
* | | | | | Merge #5114bors[bot]2020-06-283-94/+128
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5114: Cleanup cargo process handling in flycheck r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | | Cleanup cargo process handling in flycheckAleksey Kladov2020-06-282-61/+66
| | | | | | |
| * | | | | | More standard pattern for CargoAleksey Kladov2020-06-281-76/+83
| | | | | | |
| * | | | | | NamingAleksey Kladov2020-06-282-12/+11
| | | | | | |
| * | | | | | RenameAleksey Kladov2020-06-281-3/+3
| | | | | | |
| * | | | | | Make sure to join the childAleksey Kladov2020-06-281-2/+25
| | |/ / / / | |/| | | |
* / | | | | Update Chalk to released versionFlorian Diebold2020-06-281-2/+2
|/ / / / /
* | | | | Don't show ra_fixture param hintsAleksey Kladov2020-06-281-1/+2
| | | | |
* | | | | SimplifyVeetaha2020-06-271-13/+1
|/ / / /
* | | | Add support for include_bytesLaurențiu Nicola2020-06-272-0/+36
| | | |
* | | | Merge #5100bors[bot]2020-06-273-19/+60
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5100: Add support for include_str r=edwin0cheng a=lnicola r? @edwin0cheng Co-authored-by: Laurențiu Nicola <[email protected]>
| * | | | Add support for include_strLaurențiu Nicola2020-06-273-19/+60
| | |/ / | |/| |
* | | | Simplify unsafe expr collection matchPaul Daniel Faria2020-06-271-4/+3
| | | |
* | | | Improve perf of finding unsafe exprsPaul Daniel Faria2020-06-271-49/+39
| | | |
* | | | Remove unneeded code, filename from tests, fix rebasing issuesPaul Daniel Faria2020-06-2711-32/+83
| | | |
* | | | Cleanup changes leftover from previous tracking attemptPaul Daniel Faria2020-06-271-14/+16
| | | |
* | | | Revert ide highlighting changes (addressing on another branch)Paul Daniel Faria2020-06-2710-104/+10
| | | |
* | | | Remove track_parent and parent_map, replace with simple walk in missign ↵Paul Daniel Faria2020-06-273-291/+121
| | | | | | | | | | | | | | | | unsafe validator
* | | | Fix issues caused during rebasePaul Daniel Faria2020-06-271-45/+63
| | | |
* | | | unsafe: Clean up, improve tracking, add debug_assertPaul Daniel Faria2020-06-274-153/+232
| | | | | | | | | | | | | | | | | | | | | | | | Move unsafe_expressions to unsafe_validation.rs, replace vec tracking of child exprs with inline macro, add debug assert to ensure tracked children match walked children exactly
* | | | Add HighlightTag::Operator, use it for unsafe deref. Move unsafe validation ↵Paul Daniel Faria2020-06-2711-58/+81
| | | | | | | | | | | | | | | | to its own file
* | | | Account for deref token in syntax highlighting of unsafe, add test for that casePaul Daniel Faria2020-06-271-0/+1
| | | |
* | | | Track expr parents during lowering, use parent map when checking if unsafe ↵Paul Daniel Faria2020-06-274-100/+177
| | | | | | | | | | | | | | | | exprs are within unsafe blocks
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 11:28:59 +0000