Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Rename | Aleksey Kladov | 2020-07-31 | 1 | -1/+1 |
| | |||||
* | Fix GenericArgs grammar | Aleksey Kladov | 2020-07-31 | 1 | -5/+11 |
| | |||||
* | Rename TypeArgList -> GenericArgList | Aleksey Kladov | 2020-07-31 | 1 | -2/+2 |
| | |||||
* | Rename TypeRef -> Type | Aleksey Kladov | 2020-07-31 | 1 | -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 Grammar | Aleksey Kladov | 2020-07-30 | 1 | -2/+2 |
| | |||||
* | Make SemanticsScope non-generic | Laurențiu Nicola | 2020-07-01 | 1 | -10/+6 |
| | |||||
* | Deprecate hir::Path::from_ast | Aleksey Kladov | 2020-06-15 | 1 | -0/+2 |
| | |||||
* | Fix formatting | Fedor Sakharov | 2020-05-14 | 1 | -1/+1 |
| | |||||
* | Change type_arg to type_ref func | Fedor Sakharov | 2020-05-14 | 1 | -2/+1 |
| | |||||
* | Use generic_defaults and display_source_code | Fedor Sakharov | 2020-05-14 | 1 | -9/+12 |
| | |||||
* | Correctly fill default type parameters | Fedor Sakharov | 2020-05-13 | 1 | -1/+19 |
| | |||||
* | Introduce LowerCtx for path lowering | Edwin Cheng | 2020-05-01 | 1 | -0/+2 |
| | |||||
* | Generalise syntax rewriting infrastructure to allow removal of nodes | Aleksey Kladov | 2020-03-24 | 1 | -5/+7 |
| | |||||
* | Simplify | Aleksey Kladov | 2020-03-13 | 1 | -6/+3 |
| | |||||
* | One more assert | Aleksey Kladov | 2020-03-02 | 1 | -1/+6 |
| | |||||
* | Rename ast::ImplBlock -> ast::ImplDef | Aleksey Kladov | 2020-02-29 | 1 | -4/+4 |
| | |||||
* | Cleanup editing API | Aleksey Kladov | 2020-02-29 | 1 | -1/+1 |
| | |||||
* | Refactor primary IDE API | Aleksey Kladov | 2020-02-26 | 1 | -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 type | Aleksey Kladov | 2020-02-25 | 1 | -12/+13 |
| | |||||
* | More orthogonal path editing | Aleksey Kladov | 2020-01-15 | 1 | -3/+10 |
| | |||||
* | Qualify paths in 'fill match arms' assist | Florian Diebold | 2020-01-12 | 1 | -1/+1 |
| | |||||
* | Use FxHashMap | Florian Diebold | 2020-01-11 | 1 | -3/+3 |
| | |||||
* | Apply review suggestions | Florian Diebold | 2020-01-11 | 1 | -7/+8 |
| | |||||
* | Fix ordering problem between qualifying paths and substituting params | Florian Diebold | 2020-01-11 | 1 | -0/+178 |