Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Make EnumVariant a DocCommentsOwner | Jeremy A. Kolb | 2019-01-23 | 1 | -1/+1 |
| | |||||
* | Add AST/HIR for type args in path segments | Florian Diebold | 2019-01-19 | 1 | -1/+9 |
| | |||||
* | Change parsing of struct field patterns | Marcus Klaas de Vries | 2019-01-19 | 1 | -1/+6 |
| | |||||
* | Move parsing of field pattern lists to the parser (where it belongs) | Marcus Klaas de Vries | 2019-01-19 | 1 | -1/+6 |
| | |||||
* | Add initial (flawed) implementation of binding annotations | Marcus Klaas de Vries | 2019-01-19 | 1 | -1/+4 |
| | |||||
* | Create struct patterns up to the hir level | Marcus Klaas de Vries | 2019-01-19 | 1 | -3/+2 |
| | |||||
* | Add additional pattern variants | Marcus Klaas de Vries | 2019-01-19 | 1 | -2/+2 |
| | |||||
* | Update ARRAY_EXPR grammar | Hirokazu Hata | 2019-01-16 | 1 | -1/+3 |
| | |||||
* | Fix type inference for raw (byte) strings | Marcus Klaas de Vries | 2019-01-14 | 1 | -0/+4 |
| | |||||
* | Fixup tests | Marcus Klaas de Vries | 2019-01-14 | 1 | -4/+7 |
| | |||||
* | Start moving literal interpretation to the AST (WIP) | Marcus Klaas de Vries | 2019-01-14 | 1 | -2/+16 |
| | |||||
* | Update TUPLE_EXPR grammar | Hirokazu Hata | 2019-01-13 | 1 | -1/+3 |
| | |||||
* | support ref-patterns | Aleksey Kladov | 2019-01-13 | 1 | -1/+1 |
| | |||||
* | itroduce trait for ast tokens | Aleksey Kladov | 2019-01-08 | 1 | -7/+7 |
| | |||||
* | Add remaining binary operations to AST | Marcus Klaas de Vries | 2019-01-07 | 1 | -0/+1 |
| | |||||
* | Make FnScopes use hir::Expr | Florian Diebold | 2019-01-05 | 1 | -6/+4 |
| | | | | | | This was a bit complicated. I've added a wrapper type for now that does the LocalSyntaxPtr <-> ExprId translation; we might want to get rid of that or give it a nicer interface. | ||||
* | Add HIR Expr machinery | Florian Diebold | 2019-01-05 | 1 | -2/+2 |
| | |||||
* | Type the self parameter | Florian Diebold | 2019-01-04 | 1 | -1/+2 |
| | |||||
* | Add HIR for impl blocks | Florian Diebold | 2019-01-04 | 1 | -1/+5 |
| | | | | | | | | | Since we need to be able to go from def to containing impl block, as well as the other direction, and to find all impls for a certain type, a design similar to the one for modules, where we collect all impls for the whole crate and keep them in an arena, seemed fitting. The ImplBlock type, which provides the public interface, then consists only of an Arc to the arena containing all impls, and the index into it. | ||||
* | Rename ImplItem to ImplBlock | Florian Diebold | 2019-01-04 | 1 | -3/+3 |
| | | | | | rustc uses the name ImplItem for items in impls, not the impl {} block itself, which could lead to confusion. | ||||
* | visibility owner | Aleksey Kladov | 2019-01-03 | 1 | -4/+11 |
| | |||||
* | super simplistic macro expansion | Aleksey Kladov | 2018-12-28 | 1 | -1/+1 |
| | |||||
* | add macro-call node | Aleksey Kladov | 2018-12-28 | 1 | -0/+1 |
| | |||||
* | Add a hir::TypeRef as an intermediate between ast::TypeRef and ty::Ty | Florian Diebold | 2018-12-25 | 1 | -5/+5 |
| | |||||
* | Implement reference / pointer types | Florian Diebold | 2018-12-25 | 1 | -3/+3 |
| | | | | | - parse them - infer types of & and * expressions | ||||
* | Implement basic completion for fields | Florian Diebold | 2018-12-25 | 1 | -1/+1 |
| | |||||
* | Type field accesses | Florian Diebold | 2018-12-25 | 1 | -1/+1 |
| | |||||
* | Add AST definitions for struct/variant fields etc. | Florian Diebold | 2018-12-25 | 1 | -5/+7 |
| | | | | Fixes #117 | ||||
* | Infer result of struct literals, and recurse into their child expressions | Florian Diebold | 2018-12-25 | 1 | -3/+3 |
| | |||||
* | Resolve paths to defs (functions currently) during type inference | Florian Diebold | 2018-12-23 | 1 | -1/+1 |
| | |||||
* | Make let statements kind of work | Florian Diebold | 2018-12-23 | 1 | -0/+1 |
| | |||||
* | Parse integer / float types | Florian Diebold | 2018-12-23 | 1 | -1/+1 |
| | |||||
* | Add beginnings of type infrastructure | Florian Diebold | 2018-12-23 | 1 | -7/+7 |
| | |||||
* | Clarify and correct comment about multi_byte_tokens | DJMcNab | 2018-12-08 | 1 | -2/+2 |
| | |||||
* | Validate byte string literals | Adolfo Ochagavía | 2018-11-11 | 1 | -0/+1 |
| | |||||
* | Add validator for byte | Adolfo Ochagavía | 2018-11-11 | 1 | -0/+1 |
| | |||||
* | Validate string literals | Adolfo Ochagavía | 2018-11-09 | 1 | -0/+1 |
| | |||||
* | rename ROOT -> SOURCE_FILE | Aleksey Kladov | 2018-11-07 | 1 | -2/+2 |
| | |||||
* | Add some more DocCommentsOwner | Jeremy A. Kolb | 2018-11-07 | 1 | -2/+7 |
| | |||||
* | Add character literal parsing and validation | Adolfo Ochagavía | 2018-11-04 | 1 | -0/+1 |
| | |||||
* | Remove DOC_COMMENT | Jeremy A. Kolb | 2018-10-31 | 1 | -1/+0 |
| | | | | Closes #166 | ||||
* | `ast::DocCommentsOwner` which represents a documentation comment owner | Jeremy A. Kolb | 2018-10-31 | 1 | -0/+1 |
| | |||||
* | Complete crate:: paths | Aleksey Kladov | 2018-10-24 | 1 | -1/+2 |
| | |||||
* | rename gen-kinds to gen-syntax | Aleksey Kladov | 2018-10-16 | 1 | -1/+1 |
| | |||||
* | Merge #127 | bors[bot] | 2018-10-15 | 1 | -0/+1 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 127: Improve folding r=matklad a=aochagavia I was messing around with adding support for multiline comments in folding and ended up changing a bunch of other things. First of all, I am not convinced of folding groups of successive items. For instance, I don't see why it is worthwhile to be able to fold something like the following: ```rust use foo; use bar; ``` Furthermore, this causes problems if you want to fold a multiline import: ```rust use foo::{ quux }; use bar; ``` The problem is that now there are two possible folds at the same position: we could fold the first use or we could fold the import group. IMO, the only place where folding groups makes sense is when folding comments. Therefore I have **removed folding import groups in favor of folding multiline imports**. Regarding folding comments, I made it a bit more robust by requiring that comments can only be folded if they have the same flavor. So if you have a bunch of `//` comments followed by `//!` comments, you will get two separate fold groups instead of a single one. Finally, I rewrote the API in such a way that it should be trivial to add new folds. You only need to: * Create a new FoldKind * Add it to the `fold_kind` function that converts from `SyntaxKind` to `FoldKind` Fixes #113 Co-authored-by: Adolfo Ochagavía <[email protected]> | ||||
| * | Cleanup fold code and split logic to fold single elements | Adolfo Ochagavía | 2018-10-12 | 1 | -0/+1 |
| | | |||||
* | | Language Server: textDocument/signatureHelp | Jeremy A. Kolb | 2018-10-11 | 1 | -1/+1 |
|/ | | | | | | | | | | Implements a pretty barebones function signature help mechanism in the language server. Users can use `Analysis::resolve_callback()` to get basic information about a call site. Fixes #102 | ||||
* | Use Comment wrapper | Adolfo Ochagavía | 2018-10-11 | 1 | -0/+1 |
| | |||||
* | Add `cargo gen-kinds` documentation | Daniel McNab | 2018-10-04 | 1 | -1/+4 |
| | |||||
* | rename all things | Aleksey Kladov | 2018-09-16 | 1 | -0/+538 |