aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Fix underflow panic when doctests are at top of filePaul Daniel Faria2020-06-233-5/+15
| | |
* | | Merge #4999bors[bot]2020-06-235-13/+174
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | 4999: SSR: Allow matching of whole macro calls r=matklad a=davidlattimore Matching within macro calls is to come later and matching of macro calls within macro calls later still. Co-authored-by: David Lattimore <[email protected]>
| * | SSR: Allow matching of whole macro callsDavid Lattimore2020-06-225-13/+174
| |/ | | | | | | Matching within macro calls is to come later and matching of macro calls within macro calls later still.
* | Merge #5000bors[bot]2020-06-229-47/+47
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5000: Remove RelativePathBuf from fixture r=matklad a=matklad The paths in fixture are not really relative (the default one is `/main.rs`), so it doesn't make sense to use `RelativePathBuf` here. bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Remove RelativePathBuf from fixtureAleksey Kladov2020-06-229-47/+47
| | | | | | | | | | | | | | | The paths in fixture are not really relative (the default one is `/main.rs`), so it doesn't make sense to use `RelativePathBuf` here.
* | | Merge #4988bors[bot]2020-06-221-0/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4988: Don't offer to add missing fields of unknown types r=flodiebold a=lnicola Co-authored-by: LaurenČ›iu Nicola <[email protected]>
| * | | Don't offer to add missing fields of unknown typesLaurențiu Nicola2020-06-221-0/+3
| |/ /
* | | Merge #4900bors[bot]2020-06-222-0/+110
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4900: Self variant enum res fix r=BGluth a=BGluth Fixes #4789. This is my first PR for this project, so it's probably worth giving it an extra close look. A few things that I wasn't sure about: - Is `resolve_path` really the best place to perform this check? It seemed like a natural place, but perhaps there's a better place? - When handling the new variant `PathResolution::VariantDef`, I couldn't see an obvious variant of `TypeNs` to return in `in_type_ns` for Unions and Structs. Co-authored-by: BGluth <[email protected]>
| * | Enum variants with `Self::[variant]` now resolve (#4879)BGluth2020-06-221-0/+30
| | |
| * | Created goto Self enum variant testBGluth2020-06-211-0/+80
| | |
* | | Add paths::RelPath[Buf]Aleksey Kladov2020-06-221-0/+74
| |/ |/|
* | Merge #4899bors[bot]2020-06-221-72/+206
|\ \ | | | | | | | | | | | | | | | | | | | | | 4899: don't complete top level attrs inside nested attrs and add better labels r=matklad a=bnjjj close #4890 Co-authored-by: Benjamin Coenen <[email protected]>
| * | don't complete top level attrs inside nested attrs and add better labels #4899Benjamin Coenen2020-06-221-8/+1
| | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
| * | don't complete top level attrs inside nested attrs and add better labels #4899Benjamin Coenen2020-06-211-16/+105
| | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
| * | don't complete top level attrs inside nested attrs and add better labels #4890Benjamin Coenen2020-06-181-16/+8
| | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
| * | don't complete top level attrs inside nested attrs and add better labels #4890Benjamin Coenen2020-06-151-63/+123
| | | | | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]>
* | | Merge #4921bors[bot]2020-06-229-555/+1467
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4921: Allow SSR to match type references, items, paths and patterns r=davidlattimore a=davidlattimore Part of #3186 Co-authored-by: David Lattimore <[email protected]>
| * | | Allow SSR to match type references, items, paths and patternsDavid Lattimore2020-06-229-555/+1467
| | |/ | |/| | | | | | | Part of #3186
* | | Merge #4928bors[bot]2020-06-221-48/+139
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 4928: Fix renaming mod in use tree r=matklad a=unexge Fixes #4825 Co-authored-by: unexge <[email protected]>
| * | Fix renaming mod in use treeunexge2020-06-171-48/+139
| | |
* | | Update test for new serdeJeremy Kolb2020-06-211-1/+1
| | |
* | | Handle bindings after @ in patternsJonas Schievink2020-06-211-10/+24
| | |
* | | Merge #4962bors[bot]2020-06-2129-1/+222
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4962: Implement APIs for parsing expressions, types, paths, patterns and items r=davidlattimore a=davidlattimore Co-authored-by: David Lattimore <[email protected]>
| * | | Implement APIs for parsing expressions, types, paths, patterns and itemsDavid Lattimore2020-06-2129-1/+222
| | | |
* | | | Merge #4959bors[bot]2020-06-213-2/+19
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4959: Syntax highlighting for documentation comments on macro definitions r=matklad a=ltentrup Two minor changes with regards to syntax highlighting of comments attached to macro definitions. Before <img width="290" alt="Bildschirmfoto 2020-06-20 um 00 05 19" src="https://user-images.githubusercontent.com/201808/85182705-c561b500-b289-11ea-944e-0bdf6508a44f.png"> After <img width="288" alt="Bildschirmfoto 2020-06-20 um 00 03 36" src="https://user-images.githubusercontent.com/201808/85182727-d90d1b80-b289-11ea-9d2d-234731f19302.png"> Fixes #4949 Co-authored-by: Leander Tentrup <[email protected]>
| * | | | Syntax highlighting for documentation comments on macro definitionsLeander Tentrup2020-06-193-2/+19
| | | | |
* | | | | Merge #4947bors[bot]2020-06-207-59/+90
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4947: Replace `impls_in_trait` query with smarter use of `CrateImplDefs` r=matklad a=jonas-schievink `impls_in_trait` was allocating a whopping ~400 MB of RAM when running analysis-stats on r-a itself. Remove it, instead adding a query that computes a summary `CrateImplDefs` map for all transitive dependencies. This can probably still be made more efficient, but this already reduces the peak memory usage by 25% without much performance impact on analysis-stats. **Before**: ``` Total: 34.962107188s, 2083mb allocated 2141mb resident 422mb ImplsForTraitQuery (deps) 250mb CrateDefMapQueryQuery 147mb MacroArgQuery 140mb TraitSolveQuery (deps) 68mb InferQueryQuery (deps) 62mb ImplDatumQuery (deps) ``` **After**: ``` Total: 35.261100358s, 1520mb allocated 1569mb resident 250mb CrateDefMapQueryQuery 147mb MacroArgQuery 144mb TraitSolveQuery (deps) 68mb InferQueryQuery (deps) 61mb ImplDatumQuery (deps) 45mb BodyQuery 45mb ImplDatumQuery ``` Co-authored-by: Jonas Schievink <[email protected]>
| * | | | | Recursively compute impl setsJonas Schievink2020-06-191-13/+26
| | | | | |
| * | | | | Add new query to statsJonas Schievink2020-06-192-4/+5
| | | | | |
| * | | | | Don't include downstream crate in queryJonas Schievink2020-06-191-1/+2
| | | | | |
| * | | | | Replace `impls_in_trait` with `CrateImplDefs`Jonas Schievink2020-06-197-63/+79
| | |/ / / | |/| | |
* | | | | Move ReqQueue to lsp-serverAleksey Kladov2020-06-206-190/+107
| | | | |
* | | | | Merge #4961bors[bot]2020-06-204-170/+188
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4961: Centralize handing of in-flight requests r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | | Centralize handing of in-flight requestsAleksey Kladov2020-06-204-170/+188
| | | | | |
* | | | | | Merge #4958bors[bot]2020-06-204-24/+312
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4958: Infer FnSig via Fn traits r=flodiebold a=adamrk Addresses https://github.com/rust-analyzer/rust-analyzer/issues/4481. When inferring types check if the callee implements one of the builtin `Fn` traits. Also autoderef the callee before trying to figure out it's `FnSig`. Co-authored-by: adamrk <[email protected]>
| * | | | | Push obligation instead of matching on solutionadamrk2020-06-202-45/+40
| | | | | |
| * | | | | Get Output assoc type by nameadamrk2020-06-201-13/+3
| | | | | |
| * | | | | Add test for dyn Fn Outputadamrk2020-06-201-0/+68
| | | | | |
| * | | | | move tests to ra_hir_tyadamrk2020-06-202-104/+155
| | | | | |
| * | | | | Fixes to callable_sig_from_fn_traitadamrk2020-06-202-67/+72
| | | | | |
| * | | | | Make get_fn_trait a method of FnTraitadamrk2020-06-203-21/+21
| | | | | |
| * | | | | Switch back callable_sig for known fn typesadamrk2020-06-202-4/+4
| | | | | |
| * | | | | Infer FnSig from Fn traitsadamrk2020-06-195-18/+197
| | | | | |
* | | | | | Merge #4952bors[bot]2020-06-192-0/+94
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4952: Shift bound variables correctly when using assoc type shorthand r=matklad a=flodiebold Fixes #4885. Fixes #4800. Co-authored-by: Florian Diebold <[email protected]>
| * | | | | | Shift bound variables correctly when using assoc type shorthandFlorian Diebold2020-06-192-0/+94
| | |_|/ / / | |/| | | | | | | | | | | | | | | | | | | | | | Fixes #4885. Fixes #4800.
* | | | | | Merge #4951bors[bot]2020-06-192-6/+31
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4951: Don't panic on crates depending on themselves r=matklad a=flodiebold Fixes #3883. Co-authored-by: Florian Diebold <[email protected]>
| * | | | | Don't panic on crates depending on themselvesFlorian Diebold2020-06-192-6/+31
| | | | | | | | | | | | | | | | | | | | | | | | Fixes #3883.
* | | | | | Use correct substs for super trait assoc typesFlorian Diebold2020-06-193-17/+47
| |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When referring to an associated type of a super trait, we used the substs of the subtrait. That led to the #4931 crash if the subtrait had less parameters, but it could also lead to other incorrectness if just the order was different. Fixes #4931.
* | | | | Fix substs in resolve_value_path for ImplSelfVincent Rouillé2020-06-192-1/+33
|/ / / / | | | | | | | | | | | | Fixes #4953.
* | | | Merge #4851bors[bot]2020-06-195-5/+134
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4851: Add quickfix to add a struct field r=TimoFreiberg a=TimoFreiberg Related to #4563 I created a quickfix for record literals first because the NoSuchField diagnostic was already there. To offer that quickfix for FieldExprs with unknown fields I'd need to add a new diagnostic (or create a `NoSuchField` diagnostic for those cases) I think it'd make sense to make this a snippet completion (to select the generated type), but this would require changing the `Analysis` API and I'd like some feedback before I touch that. Co-authored-by: Timo Freiberg <[email protected]>