aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_assists/src/ast_transform.rs
Commit message (Collapse)AuthorAgeFilesLines
* Rename ra_syntax -> syntaxAleksey Kladov2020-08-121-14/+8
|
* Revert some FIXMEsJmPotato2020-08-111-3/+7
| | | | Signed-off-by: JmPotato <[email protected]>
* Remove redundant dependenciesJmPotato2020-08-111-3/+2
| | | | Signed-off-by: JmPotato <[email protected]>
* Address some FIXMEsJmPotato2020-08-111-8/+5
| | | | Signed-off-by: JmPotato <[email protected]>
* align names in makeAleksey Kladov2020-08-051-1/+1
|
* RenameAleksey Kladov2020-07-311-1/+1
|
* Fix GenericArgs grammarAleksey Kladov2020-07-311-5/+11
|
* Rename TypeArgList -> GenericArgListAleksey Kladov2020-07-311-2/+2
|
* Rename TypeRef -> TypeAleksey Kladov2020-07-311-6/+6
| | | | | | | | | | 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.
* Finalize impl GrammarAleksey Kladov2020-07-301-2/+2
|
* Make SemanticsScope non-genericLaurențiu Nicola2020-07-011-10/+6
|
* Deprecate hir::Path::from_astAleksey Kladov2020-06-151-0/+2
|
* Fix formattingFedor Sakharov2020-05-141-1/+1
|
* Change type_arg to type_ref funcFedor Sakharov2020-05-141-2/+1
|
* Use generic_defaults and display_source_codeFedor Sakharov2020-05-141-9/+12
|
* Correctly fill default type parametersFedor Sakharov2020-05-131-1/+19
|
* Introduce LowerCtx for path loweringEdwin Cheng2020-05-011-0/+2
|
* Generalise syntax rewriting infrastructure to allow removal of nodesAleksey Kladov2020-03-241-5/+7
|
* SimplifyAleksey Kladov2020-03-131-6/+3
|
* One more assertAleksey Kladov2020-03-021-1/+6
|
* Rename ast::ImplBlock -> ast::ImplDefAleksey Kladov2020-02-291-4/+4
|
* Cleanup editing APIAleksey Kladov2020-02-291-1/+1
|
* Refactor primary IDE APIAleksey Kladov2020-02-261-35/+30
| | | | | | | | | | This introduces the new type -- Semantics. Semantics maps SyntaxNodes to various semantic info, such as type, name resolution or macro expansions. To do so, Semantics maintains a HashMap which maps every node it saw to the file from which the node originated. This is enough to get all the necessary hir bits just from syntax.
* Replace generic with a concrete typeAleksey Kladov2020-02-251-12/+13
|
* More orthogonal path editingAleksey Kladov2020-01-151-3/+10
|
* Qualify paths in 'fill match arms' assistFlorian Diebold2020-01-121-1/+1
|
* Use FxHashMapFlorian Diebold2020-01-111-3/+3
|
* Apply review suggestionsFlorian Diebold2020-01-111-7/+8
|
* Fix ordering problem between qualifying paths and substituting paramsFlorian Diebold2020-01-111-0/+178