aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | | Document `parentModule` experimental LSP requestAleksey Kladov2020-05-254-29/+25
| | | | | |
* | | | | | Cleanup lsp extensions on the client sideAleksey Kladov2020-05-252-9/+4
| | | | | |
* | | | | | Less rust-analyzer specific onEnterAleksey Kladov2020-05-257-48/+43
|/ / / / /
* | | | | Merge #4593bors[bot]2020-05-243-20/+18
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4593: Document some rust-analyzer specific protocol extensions r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | Fix formattingAleksey Kladov2020-05-242-4/+1
| | | | | |
| * | | | | Document some rust-analyzer specific protocol extensionsAleksey Kladov2020-05-241-7/+8
| | | | | |
| * | | | | Document matchingBrace LSP requestAleksey Kladov2020-05-243-12/+12
| | | | | |
* | | | | | Handle more cases in `highlight_name_by_syntax`Matthew Jasper2020-05-241-11/+19
| | | | | |
* | | | | | Highlight `true` and `false` as literalsMatthew Jasper2020-05-249-1/+11
|/ / / / /
* | | | | Fix testsAleksey Kladov2020-05-241-25/+25
| | | | |
* | | | | Merge pull request #4548 from bnjjj/fix_4464Aleksey Kladov2020-05-248-19/+231
|\ \ \ \ \ | | | | | | | | | | | | add support of feature flag for runnables
| * | | | | add support of feature flag for runnables #4464Benjamin Coenen2020-05-242-15/+1
| | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
| * | | | | add support of feature flag for runnables #4464Benjamin Coenen2020-05-235-99/+142
| | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
| * | | | | add support of feature flag for runnables #4464Benjamin Coenen2020-05-222-21/+9
| | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
| * | | | | add support of feature flag for runnables #4464Benjamin Coenen2020-05-21116-1915/+2702
| |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
| * | | | | | add support of feature flag for runnables #4464Benjamin Coenen2020-05-217-19/+212
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
* | | | | | | Merge pull request #4495 from vsrs/fixture_metaAleksey Kladov2020-05-247-77/+326
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | Test fixtures parsing improvements
| * | | | | | | JFF, ra_fixture arg name for a code highlightingvsrs2020-05-161-9/+11
| | | | | | | |
| * | | | | | | smoke testvsrs2020-05-161-0/+6
| | | | | | | |
| * | | | | | | Propogate fixture meta to AnalysisHostvsrs2020-05-165-16/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Except crate name.
| * | | | | | | Use FixtureMeta in MockAnalysisvsrs2020-05-162-17/+85
| | | | | | | |
| * | | | | | | Remove temporary FixtureEntry parsed_meta field.vsrs2020-05-164-11/+10
| | | | | | | |
| * | | | | | | Reimplement ra_db::fixture::ParsedMetavsrs2020-05-162-51/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in terms of test_utils::FixtureMeta
| * | | | | | | parse fixture meta in test_utils cratevsrs2020-05-162-1/+101
| | | | | | | |
* | | | | | | | Merge pull request #4474 from georgewfraser/color_attrsAleksey Kladov2020-05-245-3/+11
|\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | Color attribute functions
| * | | | | | | | Color attribute functionsGeorge Fraser2020-05-195-3/+11
| | | | | | | | |
* | | | | | | | | Some FIXMEs were outdated:Julian Wollersberger2020-05-241-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Done at line 243: "Add validation of `crate` keyword not appearing in the middle of the symbol path" * Already happened: "Remove validation of unterminated literals (it is already implemented in `tokenize()`)" * Happens in `unescape()`: "Add validation of character literal containing only a single char" * Missing: "raw string literals and raw byte string literals"
* | | | | | | | | Update to rustc_lexer version 660.Julian Wollersberger2020-05-243-11/+12
| |_|_|_|_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | Change `unescape_*()` to `unescape_literal()`.
| | | | | | | |
| \ \ \ \ \ \ \
*-. \ \ \ \ \ \ \ Merge #4555 #4575bors[bot]2020-05-237-18/+179
|\ \ \ \ \ \ \ \ \ | | |_|_|_|/ / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4555: VSCode: added patchelf after download for NixOS support r=matklad a=cab404 This adds Nix support, and fixes #4542 4575: Use Chalk's built-in representations for fn items and pointers r=matklad a=flodiebold The `TypeName::FnDef` was just added; the function pointer variant has existed for a while, I just forgot about it because it's special (because fn pointers can be higher-ranked over lifetimes). We *could* also make `FnPtr` a separate `Ty` variant instead of a `TypeCtor` variant, which would make the conversion code a bit less special-casey, but it doesn't seem worth doing right now. Co-authored-by: Vladimir Serov <[email protected]> Co-authored-by: Cabia Rangris <[email protected]> Co-authored-by: Florian Diebold <[email protected]>
| | * | | | | | | Use Chalk's Ty::Function for function pointer typesFlorian Diebold2020-05-222-8/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Function pointers can be 'higher-ranked' over lifetimes, which is why they're not an application type in Chalk, but since we don't model lifetimes it doesn't matter for us yet.
| | * | | | | | | Use Chalk's built-in representation of function item typesFlorian Diebold2020-05-227-10/+128
| | | | | | | | |
* | | | | | | | | Merge #4578bors[bot]2020-05-234-7/+5
|\ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4578: Remove unnecessary clone that prevented clippy from moving on r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * | | | | | | | | And a few drive-byskjeremy2020-05-223-6/+4
| | | | | | | | | |
| * | | | | | | | | Remove unnecessary clone that prevented clippy from moving onkjeremy2020-05-221-1/+1
| | |/ / / / / / / | |/| | | | | | |
* | | | | | | | | Merge #4559bors[bot]2020-05-233-8/+17
|\ \ \ \ \ \ \ \ \ | |/ / / / / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4559: Module name on hover shows another newline after it r=matklad a=Arthamys This changes the display of hover information to add a newline between the module path of the item and the signature of the item, as suggested in #3813 **Before** ![before_3813](https://user-images.githubusercontent.com/11710698/82609224-5d517d80-9bbc-11ea-9a08-0a1558409c6b.png) **After** ![after_3813](https://user-images.githubusercontent.com/11710698/82609208-562a6f80-9bbc-11ea-8cb6-4430269c5800.png) Co-authored-by: GalilĂ©e 'Bill' Enguehard <[email protected]>
| * | | | | | | | Fix resolve_proc_macro heavy testGalilée 'Bill' Enguehard2020-05-231-1/+1
| | | | | | | | |
| * | | | | | | | Update tests to accept new hover formattingGalilée 'Bill' Enguehard2020-05-221-4/+13
| | | | | | | | |
| * | | | | | | | Fix formatting error when no modpath is presentGalilée 'Bill' Enguehard2020-05-221-3/+3
| | | | | | | | |
| * | | | | | | | Modify hover info to show module path separated by a lineGalilée 'Bill' Enguehard2020-05-221-3/+3
| | | | | | | | |
| * | | | | | | | Merge branch 'master' of github.com:rust-analyzer/rust-analyzer into ↵Galilée 'Bill' Enguehard2020-05-21409-17345/+23590
| |\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | modname_spacing
| * | | | | | | | | Add extra newline after module path in hover infoGalilée 'Bill' Enguehard2020-05-211-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes issue #3813
* | | | | | | | | | Provide missing Chalk debug methodsFlorian Diebold2020-05-222-0/+112
| | | | | | | | | |
* | | | | | | | | | Use TypeCtorId as AdtId directly, and rename the type alias StructId -> AdtIdFlorian Diebold2020-05-225-14/+14
| | | | | | | | | |
* | | | | | | | | | Split up chalk module a bitFlorian Diebold2020-05-223-958/+982
| | | | | | | | | |
* | | | | | | | | | Merge #4570bors[bot]2020-05-223-18/+277
|\ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4570: Use Chalk's built-in impls r=matklad a=flodiebold This contains two changes: - Chalk has begun adding built-in representations of primitive types; use these in our type conversion logic. There's one somewhat 'iffy' part here, namely references; we don't keep track of lifetimes, but Chalk does, so it will expect a lifetime parameter on references. If we didn't provide that, it could cause crashes in Chalk code that expects the lifetime, so I rather hackily add an (always the same) lifetime placeholder during conversion. I expect that we'll fully switch to using Chalk's types everywhere before we add lifetime support, so I think this is the best solution for now. - let Chalk know about well-known traits (from lang items), so it can apply its built-in impls. Before: ``` Total expressions: 181485 Expressions of unknown type: 2940 (1%) Expressions of partially unknown type: 2884 (1%) Type mismatches: 901 Inference: 37.821210245s, 0b allocated 0b resident Total: 53.399467609s, 0b allocated 0b resident ``` After: ``` Total expressions: 181485 Expressions of unknown type: 2923 (1%) Expressions of partially unknown type: 2879 (1%) Type mismatches: 734 Inference: 39.157752509s, 0b allocated 0b resident Total: 54.110767621s, 0b allocated 0b resident ``` (I will start splitting up `chalk.rs` in a separate PR, since it's getting pretty big...) Co-authored-by: Florian Diebold <[email protected]> Co-authored-by: Florian Diebold <[email protected]>
| * | | | | | | | | | Add some tests for Chalk built-in trait implsFlorian Diebold2020-05-221-0/+78
| | | | | | | | | | |
| * | | | | | | | | | Provide Chalk well-known traitsFlorian Diebold2020-05-222-10/+41
| | | | | | | | | | |
| * | | | | | | | | | Use Chalk's built-in representations of primitive typesFlorian Diebold2020-05-221-10/+160
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For references, we make sure Chalk actually gets a lifetime here.
* | | | | | | | | | | Merge #4571bors[bot]2020-05-228-153/+112
|\ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4571: KISS SourceChange r=matklad a=matklad The idea behind requiring the label is a noble one, but we are not really using it consistently anyway, and it should be easy to retrofit later, should we need it. bors r+ Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | | | | | | | KISS SourceChangeAleksey Kladov2020-05-228-153/+112
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The idea behind requiring the label is a noble one, but we are not really using it consistently anyway, and it should be easy to retrofit later, should we need it.