aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_assists
Commit message (Collapse)AuthorAgeFilesLines
* Rename ra_assists -> assistsAleksey Kladov2020-08-1348-16759/+0
|
* Rename ra_ide_db -> ide_dbAleksey Kladov2020-08-1313-13/+13
|
* Rename ra_hir -> hirAleksey Kladov2020-08-131-1/+1
|
* Rename ra_db -> base_dbAleksey Kladov2020-08-137-7/+7
|
* Remove ra_fmt crateAleksey Kladov2020-08-133-12/+27
|
* MinorAleksey Kladov2020-08-131-4/+5
|
* MinorAleksey Kladov2020-08-133-4/+43
|
* Remove deprecated functionAleksey Kladov2020-08-132-49/+41
|
* Cleanup **Move Guard** assistAleksey Kladov2020-08-132-117/+109
|
* **Merge Imports** assist handles selfAleksey Kladov2020-08-121-0/+27
|
* Rename ra_syntax -> syntaxAleksey Kladov2020-08-1246-67/+61
|
* Rename ra_text_edit -> text_editAleksey Kladov2020-08-123-4/+4
|
* Cleanup TextEdit APIAleksey Kladov2020-08-121-2/+2
|
* Rename ra_prof -> profileAleksey Kladov2020-08-123-4/+3
|
* Merge #5553bors[bot]2020-08-121-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5553: Add fix ranges for diagnostics r=matklad a=SomeoneToIgnore A follow-up of https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0/topic/Less.20red.20in.20the.20code Now diagnostics can apply fixes in a range that's different from the range used to highlight the diagnostics. Previous logic did not consider the fix range, having both ranges equal, which could cause a lot of red noise in the editor. Now, the fix range gets used with the fix, the diagnostics range is used for everything else which allows to improve the error highlighting. before: <img width="191" alt="image" src="https://user-images.githubusercontent.com/2690773/88590727-df9a6a00-d063-11ea-97ed-9809c1c5e6e6.png"> after: <img width="222" alt="image" src="https://user-images.githubusercontent.com/2690773/88590734-e1fcc400-d063-11ea-9b7c-25701cbd5352.png"> `MissingFields` and `MissingPatFields` diagnostics now have the fix range as `ast::RecordFieldList` of the expression with an error (as it was before this PR), and the diagnostics range as a `ast::Path` of the expression, if it's present (do you have any example of `ast::Expr::RecordLit` that has no path btw?). The rest of the diagnostics have both ranges equal, same as it was before this PR. Co-authored-by: Kirill Bulatov <[email protected]>
| * Less stubsKirill Bulatov2020-08-111-1/+1
| |
* | Replace SepBy with ItertoolsAleksey Kladov2020-08-123-8/+10
| |
* | Fix docsAleksey Kladov2020-08-121-1/+1
|/
* Revert some FIXMEsJmPotato2020-08-111-3/+7
| | | | Signed-off-by: JmPotato <[email protected]>
* Remove redundant dependenciesJmPotato2020-08-112-4/+2
| | | | Signed-off-by: JmPotato <[email protected]>
* Typo fixJmPotato2020-08-111-1/+1
| | | | Signed-off-by: JmPotato <[email protected]>
* Address some FIXMEsJmPotato2020-08-113-13/+26
| | | | Signed-off-by: JmPotato <[email protected]>
* Remove Option<...> from result of Crate::root_modulePaul Daniel Faria2020-08-091-1/+1
| | | | | There doesn't seem to be any need for it, and removing it simplies several paths of code that depend on it.
* Add support for extern cratePaul Daniel Faria2020-08-081-1/+1
| | | | | This adds syntax highlighting, hover and goto def functionality for extern crate
* align names in makeAleksey Kladov2020-08-059-16/+15
|
* Merge #5648bors[bot]2020-08-054-0/+424
|\ | | | | | | | | | | | | | | 5648: Add expand glob import assist r=jonas-schievink a=unexge closes https://github.com/rust-analyzer/rust-analyzer/issues/5557 Co-authored-by: unexge <[email protected]>
| * Pattern match on slice elements instead of using `.first().unwrap()`unexge2020-08-051-7/+6
| |
| * Look for trait methods in expand glob import assistunexge2020-08-051-13/+65
| |
| * Simplify `find_mod_path` with use of `node.ancestors`unexge2020-08-031-20/+1
| |
| * Generate doctestunexge2020-08-022-1/+28
| |
| * Rename ast::UseItem to ast::Useunexge2020-08-021-1/+1
| |
| * Add expand glob import assistunexge2020-08-023-0/+365
| |
* | do not add to `pub use` statementsJacob Rothstein2020-08-032-1/+44
| |
* | Merge #5628bors[bot]2020-08-031-1/+1
|\ \ | |/ |/| | | | | | | | | | | 5628: Rename test modules r=matklad a=lnicola Co-authored-by: Laurențiu Nicola <[email protected]>
| * Rename test modulesLaurențiu Nicola2020-07-311-1/+1
| |
* | Update grammarAleksey Kladov2020-08-011-1/+1
| |
* | Unify naming of tuple fieldsAleksey Kladov2020-07-311-2/+2
| |
* | RenameAleksey Kladov2020-07-312-6/+3
| |
* | Rename BindPat -> IdentPatAleksey Kladov2020-07-314-4/+4
| |
* | Rename PalceholderPat -> WildcardPatAleksey Kladov2020-07-313-15/+12
| |
* | Allign RecordPat with RecordExprAleksey Kladov2020-07-311-2/+2
| |
* | Fix GenericArgs grammarAleksey Kladov2020-07-311-5/+11
| |
* | Rename TypeArgList -> GenericArgListAleksey Kladov2020-07-311-2/+2
| |
* | MinorAleksey Kladov2020-07-311-1/+0
| |
* | Rename LambdaExpr -> ClosureExprAleksey Kladov2020-07-311-2/+2
| |
* | Item is a StmtAleksey Kladov2020-07-311-0/+2
| |
* | Reame PlaceholderType -> InferTypeAleksey Kladov2020-07-311-1/+1
| |
* | Rename TypeRef -> TypeAleksey Kladov2020-07-313-8/+8
|/ | | | | | | | | | The TypeRef name comes from IntelliJ days, where you often have both type *syntax* as well as *semantical* representation of types in scope. And naming both Type is confusing. In rust-analyzer however, we use ast types as `ast::Type`, and have many more semantic counterparts to ast types, so avoiding name clash here is just confusing.
* Use ty to access most TypeRefsAleksey Kladov2020-07-302-2/+2
|
* Remove TypeAscriptionOwnerAleksey Kladov2020-07-303-17/+12
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 03:10:21 +0100